From 3d8c51f87087369900bde14686d34669b013e0a0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?R=C3=A9mi=20Verschelde?= <rverschelde@gmail.com>
Date: Tue, 4 Dec 2018 23:35:09 +0100
Subject: [PATCH] Sync Weblate translations with Weblate template

---
 weblate/ar.po      | 2156 ++++++++++++++++++++-----------------
 weblate/ca.po      | 2157 ++++++++++++++++++++-----------------
 weblate/cs.po      | 2155 ++++++++++++++++++++-----------------
 weblate/da.po      | 2157 ++++++++++++++++++++-----------------
 weblate/de.po      | 2173 +++++++++++++++++++++-----------------
 weblate/el.po      | 2156 ++++++++++++++++++++-----------------
 weblate/es.po      | 2218 +++++++++++++++++++++-----------------
 weblate/es_MX.po   | 2171 +++++++++++++++++++++-----------------
 weblate/fa.po      | 2156 ++++++++++++++++++++-----------------
 weblate/fi.po      | 2178 +++++++++++++++++++++-----------------
 weblate/fil.po     | 2155 ++++++++++++++++++++-----------------
 weblate/fr.po      | 2208 +++++++++++++++++++++-----------------
 weblate/he.po      | 2155 ++++++++++++++++++++-----------------
 weblate/hi.po      | 2156 ++++++++++++++++++++-----------------
 weblate/hu.po      | 2157 ++++++++++++++++++++-----------------
 weblate/id.po      | 2157 ++++++++++++++++++++-----------------
 weblate/it.po      | 2160 ++++++++++++++++++++-----------------
 weblate/ja.po      | 2157 ++++++++++++++++++++-----------------
 weblate/jbo.po     | 2155 ++++++++++++++++++++-----------------
 weblate/ko.po      | 2230 ++++++++++++++++++++++-----------------
 weblate/lt.po      | 2155 ++++++++++++++++++++-----------------
 weblate/ms.po      | 2157 ++++++++++++++++++++-----------------
 weblate/nb.po      | 2155 ++++++++++++++++++++-----------------
 weblate/nl.po      | 2157 ++++++++++++++++++++-----------------
 weblate/pl.po      | 2200 +++++++++++++++++++++-----------------
 weblate/pt_BR.po   | 2224 +++++++++++++++++++++-----------------
 weblate/pt_PT.po   | 2227 ++++++++++++++++++++++-----------------
 weblate/ro.po      | 2157 ++++++++++++++++++++-----------------
 weblate/ru.po      | 2191 +++++++++++++++++++++-----------------
 weblate/sk.po      | 2155 ++++++++++++++++++++-----------------
 weblate/sl.po      | 2156 ++++++++++++++++++++-----------------
 weblate/sr_Latn.po | 2156 ++++++++++++++++++++-----------------
 weblate/sv.po      | 2159 ++++++++++++++++++++-----------------
 weblate/te.po      | 2155 ++++++++++++++++++++-----------------
 weblate/th.po      | 2156 ++++++++++++++++++++-----------------
 weblate/tr.po      | 2155 ++++++++++++++++++++-----------------
 weblate/uk.po      | 2158 ++++++++++++++++++++-----------------
 weblate/vi.po      | 2157 ++++++++++++++++++++-----------------
 weblate/zh_CN.po   | 2520 +++++++++++++++++++++++++-------------------
 weblate/zh_TW.po   | 2157 ++++++++++++++++++++-----------------
 40 files changed, 47861 insertions(+), 39213 deletions(-)

diff --git a/weblate/ar.po b/weblate/ar.po
index d4aa6650d0..15430fb5db 100644
--- a/weblate/ar.po
+++ b/weblate/ar.po
@@ -14,7 +14,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-10-22 21:22+0000\n"
 "Last-Translator: Mohamed El-Baz <albaz2000eg@gmail.com>\n"
 "Language-Team: Arabic <https://hosted.weblate.org/projects/godot-engine/"
@@ -76,13 +76,14 @@ msgstr ""
 "تحسينها من خلال تبليغنا!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "قم بتقديم issue أو pull request على `GitHub repository <https://github.com/"
 "godotengine/godot-docs/issues>`_, ساعدنا على `ترجمة التوثيق <https://hosted."
@@ -154,7 +155,6 @@ msgstr "حول"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -173,6 +173,7 @@ msgstr "حول"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -353,9 +354,9 @@ msgstr ""
 
 #: ../../docs/about/introduction.rst:85
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1313,7 +1314,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1780,7 +1781,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1855,13 +1856,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2105,8 +2106,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2130,7 +2131,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2204,7 +2205,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2218,7 +2219,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2558,6 +2559,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "إشارات"
@@ -3028,7 +3030,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3154,7 +3156,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3364,7 +3366,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3462,7 +3464,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3490,7 +3492,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -3988,7 +3990,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4045,8 +4047,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4122,7 +4124,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4219,7 +4221,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4305,14 +4307,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4421,7 +4423,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4467,7 +4469,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4507,7 +4509,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4548,9 +4550,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4638,7 +4640,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4755,7 +4757,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4803,7 +4805,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4945,7 +4947,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5053,7 +5055,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5077,7 +5079,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5404,9 +5406,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5436,8 +5439,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5477,8 +5481,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6380,7 +6384,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6449,9 +6453,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6468,12 +6472,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6496,8 +6500,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6673,10 +6678,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6755,16 +6760,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6775,7 +6780,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6817,7 +6822,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6844,7 +6849,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -6993,7 +6998,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7008,7 +7013,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7086,7 +7091,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7113,7 +7118,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7250,9 +7255,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7321,16 +7326,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7347,14 +7352,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7385,16 +7390,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7456,7 +7461,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7486,7 +7491,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7632,7 +7637,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7662,7 +7667,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7694,7 +7699,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8129,9 +8134,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8441,7 +8446,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8521,7 +8526,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8638,12 +8643,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8695,7 +8700,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10131,7 +10136,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10511,7 +10516,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10590,7 +10595,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10616,7 +10621,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10827,9 +10832,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10874,7 +10879,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10920,7 +10925,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10931,7 +10936,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11002,7 +11007,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11022,7 +11027,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19404,7 +19409,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "ادوات"
 
@@ -22339,8 +22344,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22553,9 +22557,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24540,7 +24544,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25271,437 +25275,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27467,7 +27040,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27477,7 +27050,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42774,9 +42347,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42826,9 +42399,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42882,46 +42455,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42929,7 +42500,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42938,7 +42509,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42946,7 +42517,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42956,7 +42527,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -42967,19 +42538,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -42987,13 +42558,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43001,7 +42572,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43010,7 +42581,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43024,7 +42595,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43033,7 +42604,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43041,10 +42612,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44009,6 +43580,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46924,6 +46500,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51469,11 +51471,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51667,73 +51669,70 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51741,131 +51740,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51873,55 +51868,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51932,22 +51927,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51956,7 +51951,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -51964,11 +51959,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -51977,42 +51972,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52022,7 +52024,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52031,7 +52033,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52039,58 +52041,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54181,7 +54380,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54189,18 +54388,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54208,23 +54407,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54232,35 +54431,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54269,103 +54468,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54373,20 +54572,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54425,11 +54624,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54439,24 +54650,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54465,7 +54676,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54473,18 +54684,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54494,7 +54705,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54503,37 +54714,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54541,63 +54752,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54605,13 +54816,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54619,7 +54830,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54627,25 +54838,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54653,30 +54864,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54684,7 +54895,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54693,25 +54904,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54722,46 +54933,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54770,68 +54981,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54839,7 +55050,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54848,11 +55059,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54860,114 +55071,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55034,37 +55245,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55072,61 +55283,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55146,18 +55357,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55165,11 +55376,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55177,37 +55388,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55268,27 +55479,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55296,24 +55507,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55321,29 +55519,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55351,35 +55549,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55387,40 +55585,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55428,131 +55626,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55572,29 +55770,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55605,17 +55803,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55725,6 +55923,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55809,61 +56011,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55872,13 +56074,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55887,11 +56089,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55899,14 +56101,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55914,14 +56116,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55930,14 +56132,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55947,7 +56149,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55956,7 +56158,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -55965,7 +56167,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -55996,7 +56198,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56006,7 +56208,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56014,14 +56216,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56029,21 +56231,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56052,7 +56254,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56062,7 +56264,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/ca.po b/weblate/ca.po
index 0331422693..06c347dda1 100644
--- a/weblate/ca.po
+++ b/weblate/ca.po
@@ -9,7 +9,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-09-12 03:14+0000\n"
 "Last-Translator: Roger Blanco Ribera <roger.blancoribera@gmail.com>\n"
 "Language-Team: Catalan <https://hosted.weblate.org/projects/godot-engine/"
@@ -73,13 +73,14 @@ msgstr ""
 "clara o no trobeu la informació que cercàveu, no dubteu a  fer-nos-ho saber!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Envieu-nos un problema o un pull request en el repositori `GitHub <https://"
 "github.com/godotengine/godot-docs/issues>`_, ajuda'ns a traduir la "
@@ -152,7 +153,6 @@ msgstr "Quant a"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -171,6 +171,7 @@ msgstr "Quant a"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -371,10 +372,11 @@ msgstr ""
 "motor i el desenvolupament de mòduls C++ o connectors per l'editor."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1410,7 +1412,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1877,7 +1879,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1952,13 +1954,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2202,8 +2204,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2227,7 +2229,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2301,7 +2303,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2315,7 +2317,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2655,6 +2657,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr ""
@@ -3125,7 +3128,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3251,7 +3254,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3460,7 +3463,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3558,7 +3561,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3586,7 +3589,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -4084,7 +4087,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4140,8 +4143,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4217,7 +4220,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4314,7 +4317,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4400,14 +4403,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4516,7 +4519,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4562,7 +4565,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4602,7 +4605,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4643,9 +4646,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4733,7 +4736,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4850,7 +4853,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4898,7 +4901,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -5040,7 +5043,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5148,7 +5151,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5172,7 +5175,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5499,9 +5502,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5531,8 +5535,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5572,8 +5577,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6475,7 +6480,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6544,9 +6549,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6563,12 +6568,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6591,8 +6596,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6768,10 +6774,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6850,16 +6856,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6870,7 +6876,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6912,7 +6918,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6939,7 +6945,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -7088,7 +7094,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7103,7 +7109,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7181,7 +7187,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7208,7 +7214,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7345,9 +7351,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7416,16 +7422,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7442,14 +7448,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7480,16 +7486,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7551,7 +7557,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7581,7 +7587,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7727,7 +7733,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7757,7 +7763,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7789,7 +7795,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8224,9 +8230,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8537,7 +8543,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8617,7 +8623,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8734,12 +8740,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8791,7 +8797,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10227,7 +10233,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10607,7 +10613,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10686,7 +10692,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10712,7 +10718,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10924,9 +10930,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10971,7 +10977,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -11017,7 +11023,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -11028,7 +11034,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11099,7 +11105,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11119,7 +11125,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19494,7 +19500,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -22428,8 +22434,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22642,9 +22647,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24631,7 +24636,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25362,437 +25367,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27558,7 +27132,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27568,7 +27142,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42861,9 +42435,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42913,9 +42487,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42969,46 +42543,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -43016,7 +42588,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -43025,7 +42597,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -43033,7 +42605,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -43043,7 +42615,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -43054,19 +42626,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -43074,13 +42646,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43088,7 +42660,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43097,7 +42669,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43111,7 +42683,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43120,7 +42692,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43128,10 +42700,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44096,6 +43668,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -47011,6 +46588,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51555,11 +51558,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51753,45 +51756,41 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -51800,29 +51799,30 @@ msgstr ""
 "A més, també pots fer fer una ullada als diferents `projectes de demostració "
 "<https://github.com/godotengine/godot-demo-projects>`_."
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51830,131 +51830,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51962,55 +51958,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -52021,22 +52017,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -52045,7 +52041,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -52053,11 +52049,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -52066,42 +52062,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52111,7 +52114,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52120,7 +52123,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52128,58 +52131,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54270,7 +54470,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54278,18 +54478,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54297,23 +54497,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54321,35 +54521,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54358,103 +54558,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54462,20 +54662,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54514,11 +54714,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54528,24 +54740,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54554,7 +54766,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54562,18 +54774,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54583,7 +54795,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54592,37 +54804,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54630,63 +54842,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54694,13 +54906,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54708,7 +54920,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54716,25 +54928,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54742,30 +54954,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54773,7 +54985,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54782,25 +54994,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54811,46 +55023,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54859,68 +55071,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54928,7 +55140,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54937,11 +55149,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54949,114 +55161,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55123,37 +55335,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55161,61 +55373,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55235,18 +55447,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55254,11 +55466,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55266,37 +55478,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55357,27 +55569,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55385,24 +55597,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55410,29 +55609,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55440,35 +55639,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55476,40 +55675,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55517,131 +55716,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55661,29 +55860,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55694,17 +55893,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55814,6 +56013,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55898,61 +56101,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55961,13 +56164,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55976,11 +56179,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55988,14 +56191,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -56003,14 +56206,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -56019,14 +56222,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -56036,7 +56239,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -56045,7 +56248,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -56054,7 +56257,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56085,7 +56288,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56095,7 +56298,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56103,14 +56306,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56118,21 +56321,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56141,7 +56344,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56151,7 +56354,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/cs.po b/weblate/cs.po
index f4947084d4..d75b6b8874 100644
--- a/weblate/cs.po
+++ b/weblate/cs.po
@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-12-04 22:23+0000\n"
 "Last-Translator: Vojtěch Šamla <auzkok@seznam.cz>\n"
 "Language-Team: Czech <https://hosted.weblate.org/projects/godot-engine/godot-"
@@ -67,9 +67,9 @@ msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 
 #: ../../docs/index.rst:43
@@ -135,7 +135,6 @@ msgstr "O aplikaci"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -154,6 +153,7 @@ msgstr "O aplikaci"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -301,9 +301,9 @@ msgstr ""
 
 #: ../../docs/about/introduction.rst:85
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1244,7 +1244,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1711,7 +1711,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1786,13 +1786,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2036,8 +2036,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2061,7 +2061,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2135,7 +2135,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2149,7 +2149,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2489,6 +2489,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Signály"
@@ -2961,7 +2962,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3088,7 +3089,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3300,7 +3301,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3398,7 +3399,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3426,7 +3427,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -3924,7 +3925,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -3981,8 +3982,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4058,7 +4059,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4155,7 +4156,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4241,14 +4242,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4358,7 +4359,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4404,7 +4405,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4444,7 +4445,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4485,9 +4486,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4575,7 +4576,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4692,7 +4693,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4740,7 +4741,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4882,7 +4883,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -4990,7 +4991,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5014,7 +5015,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5341,9 +5342,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5373,8 +5375,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5414,8 +5417,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6317,7 +6320,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6386,9 +6389,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6405,12 +6408,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6433,8 +6436,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6610,10 +6614,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6692,16 +6696,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6712,7 +6716,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6754,7 +6758,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6781,7 +6785,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -6930,7 +6934,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -6945,7 +6949,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7023,7 +7027,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7050,7 +7054,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7187,9 +7191,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7258,16 +7262,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7284,14 +7288,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7322,16 +7326,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7393,7 +7397,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7423,7 +7427,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7569,7 +7573,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7599,7 +7603,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7631,7 +7635,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8066,9 +8070,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8378,7 +8382,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8458,7 +8462,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8575,12 +8579,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8632,7 +8636,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10070,7 +10074,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10450,7 +10454,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10529,7 +10533,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10555,7 +10559,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10766,9 +10770,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10813,7 +10817,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10859,7 +10863,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10870,7 +10874,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -10941,7 +10945,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -10961,7 +10965,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19346,7 +19350,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "Nástroje"
 
@@ -22280,8 +22284,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22494,9 +22497,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24482,7 +24485,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25214,437 +25217,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27410,7 +26982,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27420,7 +26992,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42716,9 +42288,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42768,9 +42340,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42824,46 +42396,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42871,7 +42441,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42880,7 +42450,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42888,7 +42458,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42898,7 +42468,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -42909,19 +42479,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -42929,13 +42499,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -42943,7 +42513,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -42952,7 +42522,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -42966,7 +42536,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -42975,7 +42545,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -42983,10 +42553,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -43951,6 +43521,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46869,6 +46444,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51414,11 +51415,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51612,73 +51613,70 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51686,131 +51684,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51818,55 +51812,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51877,22 +51871,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51901,7 +51895,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -51909,11 +51903,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -51922,42 +51916,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -51967,7 +51968,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -51976,7 +51977,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -51984,58 +51985,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54125,7 +54323,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54133,18 +54331,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54152,23 +54350,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54176,35 +54374,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54213,103 +54411,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54317,20 +54515,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54369,11 +54567,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54383,24 +54593,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54409,7 +54619,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54417,18 +54627,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54438,7 +54648,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54447,37 +54657,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54485,63 +54695,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54549,13 +54759,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54563,7 +54773,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54571,25 +54781,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54597,30 +54807,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54628,7 +54838,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54637,25 +54847,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54666,46 +54876,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54714,68 +54924,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54783,7 +54993,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54792,11 +55002,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54804,114 +55014,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -54978,37 +55188,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55016,61 +55226,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55090,18 +55300,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55109,11 +55319,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55121,37 +55331,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55212,27 +55422,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55240,24 +55450,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55265,29 +55462,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55295,35 +55492,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55331,40 +55528,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55372,131 +55569,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55516,29 +55713,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55549,17 +55746,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "Spustit"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55669,6 +55866,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55753,61 +55954,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55816,13 +56017,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55831,11 +56032,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55843,14 +56044,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55858,14 +56059,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55874,14 +56075,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55891,7 +56092,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55900,7 +56101,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -55909,7 +56110,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -55940,7 +56141,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -55950,7 +56151,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -55958,14 +56159,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -55973,21 +56174,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -55996,7 +56197,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56006,7 +56207,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/da.po b/weblate/da.po
index d7c3082e32..9fd20c558b 100644
--- a/weblate/da.po
+++ b/weblate/da.po
@@ -9,7 +9,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-08-10 13:36+0000\n"
 "Last-Translator: Christoffer Schindel <ceas@outlook.com>\n"
 "Language-Team: Danish <https://hosted.weblate.org/projects/godot-engine/"
@@ -73,13 +73,14 @@ msgstr ""
 "gøre platformen bedre ved at fortælle os det!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Insend en \"issue\" eller \"pull request\" på vores `GitHub repository "
 "<https://github.com/godotengine/godot-docs/issues>`_, hjælp os med at "
@@ -152,7 +153,6 @@ msgstr "Om"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -171,6 +171,7 @@ msgstr "Om"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -369,10 +370,11 @@ msgstr ""
 "udvikling af C++ moduler eller plugins."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1376,7 +1378,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1843,7 +1845,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1918,13 +1920,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2168,8 +2170,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2193,7 +2195,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2267,7 +2269,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2281,7 +2283,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2621,6 +2623,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr ""
@@ -3091,7 +3094,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3217,7 +3220,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3426,7 +3429,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3524,7 +3527,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3552,7 +3555,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -4050,7 +4053,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4106,8 +4109,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4183,7 +4186,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4280,7 +4283,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4366,14 +4369,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4482,7 +4485,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4528,7 +4531,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4568,7 +4571,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4609,9 +4612,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4699,7 +4702,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4816,7 +4819,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4864,7 +4867,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -5006,7 +5009,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5114,7 +5117,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5138,7 +5141,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5465,9 +5468,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5497,8 +5501,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5538,8 +5543,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6441,7 +6446,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6510,9 +6515,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6529,12 +6534,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6557,8 +6562,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6734,10 +6740,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6816,16 +6822,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6836,7 +6842,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6878,7 +6884,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6905,7 +6911,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -7054,7 +7060,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7069,7 +7075,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7147,7 +7153,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7174,7 +7180,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7311,9 +7317,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7382,16 +7388,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7408,14 +7414,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7446,16 +7452,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7517,7 +7523,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7547,7 +7553,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7693,7 +7699,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7723,7 +7729,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7755,7 +7761,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8190,9 +8196,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8503,7 +8509,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8583,7 +8589,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8700,12 +8706,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8757,7 +8763,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10193,7 +10199,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10573,7 +10579,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10652,7 +10658,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10678,7 +10684,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10890,9 +10896,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10937,7 +10943,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10983,7 +10989,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10994,7 +11000,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11065,7 +11071,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11085,7 +11091,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19459,7 +19465,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -22393,8 +22399,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22607,9 +22612,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24596,7 +24601,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25327,437 +25332,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27523,7 +27097,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27533,7 +27107,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42827,9 +42401,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42879,9 +42453,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42935,46 +42509,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42982,7 +42554,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42991,7 +42563,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42999,7 +42571,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -43009,7 +42581,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -43020,19 +42592,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -43040,13 +42612,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43054,7 +42626,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43063,7 +42635,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43077,7 +42649,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43086,7 +42658,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43094,10 +42666,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44062,6 +43634,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46977,6 +46554,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51521,11 +51524,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51719,45 +51722,41 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -51766,29 +51765,30 @@ msgstr ""
 "Foruden denne dokumentation kan du evt. tage et kig på de forskellige `Godot "
 "demo projects <https://github.com/godotengine/godot-demo-projects>`_."
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51796,131 +51796,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51928,55 +51924,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51987,22 +51983,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -52011,7 +52007,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -52019,11 +52015,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -52032,42 +52028,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52077,7 +52080,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52086,7 +52089,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52094,58 +52097,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54236,7 +54436,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54244,18 +54444,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54263,23 +54463,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54287,35 +54487,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54324,103 +54524,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54428,20 +54628,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54480,11 +54680,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54494,24 +54706,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54520,7 +54732,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54528,18 +54740,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54549,7 +54761,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54558,37 +54770,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54596,63 +54808,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54660,13 +54872,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54674,7 +54886,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54682,25 +54894,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54708,30 +54920,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54739,7 +54951,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54748,25 +54960,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54777,46 +54989,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54825,68 +55037,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54894,7 +55106,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54903,11 +55115,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54915,114 +55127,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55089,37 +55301,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55127,61 +55339,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55201,18 +55413,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55220,11 +55432,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55232,37 +55444,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55323,27 +55535,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55351,24 +55563,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55376,29 +55575,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55406,35 +55605,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55442,40 +55641,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55483,131 +55682,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55627,29 +55826,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55660,17 +55859,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55780,6 +55979,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55864,61 +56067,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55927,13 +56130,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55942,11 +56145,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55954,14 +56157,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55969,14 +56172,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55985,14 +56188,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -56002,7 +56205,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -56011,7 +56214,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -56020,7 +56223,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56051,7 +56254,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56061,7 +56264,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56069,14 +56272,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56084,21 +56287,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56107,7 +56310,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56117,7 +56320,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/de.po b/weblate/de.po
index 05ea828658..6eb7051ea7 100644
--- a/weblate/de.po
+++ b/weblate/de.po
@@ -44,7 +44,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-12-04 22:23+0000\n"
 "Last-Translator: ssantos <ssantos@web.de>\n"
 "Language-Team: German <https://hosted.weblate.org/projects/godot-engine/"
@@ -110,13 +110,14 @@ msgstr ""
 "Bescheid gibst!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Schicke eine Frage oder einen Pull Request an das`GitHub Repository <https://"
 "github.com/godotengine/godot-docs/issues>`_, hilf uns  `die Dokumentation "
@@ -191,7 +192,6 @@ msgstr "Über"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -210,6 +210,7 @@ msgstr "Über"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -414,10 +415,11 @@ msgstr ""
 "der Engine und zur Entwicklung von C++-Modulen oder Editor Plugins."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1679,7 +1681,8 @@ msgid "It can be extended (to have more functions)."
 msgstr "Er kann erweitert werden (um Funktionen hinzuzufügen)."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+#, fuzzy
+msgid "It can be added to another node as a child."
 msgstr "Er kann anderen Nodes als Unterobjekt hinzugefügt werden."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -2315,13 +2318,14 @@ msgstr ""
 "du das Instanziieren (entweder im Code oder direkt im Editor) verwenden."
 
 #: ../../docs/getting_started/step_by_step/instancing_continued.rst:43
+#, fuzzy
 msgid ""
 "A lot of time spent in programming games (or software in general) is on "
 "designing an architecture and fitting game components to that architecture. "
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 "Beim Programmieren von Spielen (oder Software allgemein) wird viel Zeit "
@@ -2432,16 +2436,18 @@ msgstr ""
 "die Möglichkeit zusätzliche Sprachen dynamisch hinzuzufügen!"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
+#, fuzzy
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 "Das ist großartig, da die große Anzahl Sprachen mehr Flexibiliät bieten, "
 "aber es macht unsere Arbeit, diese zu unterstützen, auch schwerer."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
+#, fuzzy
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2767,9 +2773,10 @@ msgstr ""
 "Optionen."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
+#, fuzzy
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 "In GDScript bestimmt der Dateiname die Klasse, daher ist der Klassenname "
 "nicht editierbar."
@@ -2799,9 +2806,10 @@ msgstr ""
 "und als Skripteigenschaft im Inspektortab:"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
+#, fuzzy
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 "Um das Skript zu bearbeiten, wähle eine der erwähnten Schlatflächen, welche "
@@ -2904,11 +2912,12 @@ msgstr ""
 "Funktionsaufrufes."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:205
+#, fuzzy
 msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 "Der obere linke Bereich zeigt eine Liste mit den Nodes in der Szene, mit der "
 "Signalquelle hervorgehoben in Rot. Wähle hier das Panel Node aus. Nach der "
@@ -2929,9 +2938,10 @@ msgstr ""
 "Signalverbindung hergestellt wird."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
+#, fuzzy
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 "Und damit schließt der Leitfaden für das grafische Interface ab. Da dies "
@@ -3407,6 +3417,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Signale"
@@ -4000,10 +4011,11 @@ msgstr ""
 "ermitteln:"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:198
+#, fuzzy
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 "Nun können wir mit der Funktion ``_process()`` definieren, was der Spieler "
 "tun soll. ``_process()`` wird mit jedem Frame aufgerufen, also werden wir es "
@@ -4188,10 +4200,11 @@ msgstr ""
 "Zuweisung oben:"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:372
+#, fuzzy
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 "Spiele die Szene noch einmal ab und überprüfe, ob die Animationen in jede "
 "der Richtungen korrekt sind. Wenn Du sicher bist, dass die Bewegung korrekt "
@@ -4479,8 +4492,9 @@ msgstr ""
 "Siehe :ref:`doc_instancing`, um mehr über das Instanzieren zu erfahren."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
+#, fuzzy
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 "Füge nun die folgenden Nodes als Kinder von ``Main`` hinzu und benenne sie "
@@ -4611,8 +4625,9 @@ msgid "Main script"
 msgstr "Main Skript"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
+#, fuzzy
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 "Füge ein Skript zu ``Main`` hinzu. Am Anfang des Skripts verwenden wir "
@@ -4653,8 +4668,9 @@ msgstr ""
 "die anderen beiden Timer. ``ScoreTimer`` erhöht die Punktzahl um 1."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
+#, fuzzy
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -5226,7 +5242,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -5283,8 +5299,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -5361,7 +5377,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -5460,9 +5476,10 @@ msgstr ""
 "Dateien:"
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
+#, fuzzy
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -5559,14 +5576,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -5676,7 +5693,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -5722,7 +5739,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -5762,7 +5779,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -5803,9 +5820,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -5893,7 +5910,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -6010,7 +6027,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -6058,7 +6075,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -6200,7 +6217,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -6308,7 +6325,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -6332,7 +6349,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -6659,9 +6676,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -6691,8 +6709,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -6732,8 +6751,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -7635,7 +7654,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -7704,9 +7723,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -7723,12 +7742,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -7751,8 +7770,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -7928,10 +7948,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -8010,16 +8030,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -8030,7 +8050,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -8072,7 +8092,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -8099,7 +8119,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -8248,7 +8268,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -8263,7 +8283,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -8341,7 +8361,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -8368,7 +8388,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -8505,9 +8525,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -8576,16 +8596,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -8602,14 +8622,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -8640,16 +8660,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -8711,7 +8731,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -8742,7 +8762,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -8889,7 +8909,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -8919,7 +8939,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -8951,7 +8971,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -9386,9 +9406,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -9698,7 +9718,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -9778,7 +9798,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -9895,12 +9915,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -9952,7 +9972,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -11509,7 +11529,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -11920,8 +11940,9 @@ msgid "Remove ``case``"
 msgstr "Entferne ``case``"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
+#, fuzzy
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 "Entfernt jedes ``break``. Sollte das standardmäßige ``break`` ungewünscht "
@@ -12010,7 +12031,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -12036,7 +12057,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -12266,9 +12287,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -12313,7 +12334,7 @@ msgstr "Arrays exportieren"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -12359,7 +12380,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -12370,7 +12391,7 @@ msgstr "Werkzeug-Modus"
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -12442,7 +12463,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -12462,7 +12483,7 @@ msgstr "Co-Routinen & Signale"
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -21045,7 +21066,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "Werkzeuge"
 
@@ -23985,8 +24006,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -24199,9 +24219,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -26204,7 +26224,7 @@ msgstr ":ref:`String <class_String>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
 #, fuzzy
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ":ref:`Color <class_Color>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -26939,437 +26959,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -29137,7 +28726,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -29147,7 +28736,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -44456,9 +44045,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -44508,9 +44097,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -44564,47 +44153,45 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 #, fuzzy
 msgid "Coloring the planet"
 msgstr "Konfigurieren des Projektes"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -44612,7 +44199,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -44621,7 +44208,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -44629,7 +44216,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -44639,7 +44226,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -44650,19 +44237,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -44670,13 +44257,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -44684,7 +44271,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -44693,7 +44280,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -44707,7 +44294,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -44716,7 +44303,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -44724,10 +44311,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -45697,6 +45284,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -48618,6 +48210,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -53169,11 +53187,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -53367,46 +53385,42 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 #, fuzzy
 msgid "Setting up the project"
 msgstr "Projekt importieren"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -53416,29 +53430,30 @@ msgstr ""
 "auf die verschieden `Godot Demoprojekte <https://github.com/godotengine/"
 "godot-demo-projects>`_ werfen."
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -53446,132 +53461,128 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 #, fuzzy
 msgid "Creating a simple plugin"
 msgstr "Erstellen eines C# Skripts"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -53579,55 +53590,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -53638,22 +53649,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -53662,7 +53673,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -53670,11 +53681,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -53683,42 +53694,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -53728,7 +53746,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -53737,7 +53755,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -53745,58 +53763,256 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+#, fuzzy
+msgid "Adding properties"
+msgstr "Er hat veränderbare Eigenschaften."
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -55890,7 +56106,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -55898,18 +56114,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -55917,23 +56133,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -55941,35 +56157,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -55978,103 +56194,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -56082,20 +56298,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -56134,11 +56350,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -56148,24 +56376,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -56174,7 +56402,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -56182,18 +56410,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -56203,7 +56431,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -56212,37 +56440,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -56250,63 +56478,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -56314,13 +56542,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -56328,7 +56556,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -56336,25 +56564,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -56362,30 +56590,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -56393,7 +56621,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -56402,25 +56630,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -56431,46 +56659,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -56479,68 +56707,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -56548,7 +56776,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -56557,11 +56785,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -56569,114 +56797,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -56743,37 +56971,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -56781,61 +57009,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -56855,18 +57083,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -56874,11 +57102,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -56886,37 +57114,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -56977,27 +57205,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -57005,24 +57233,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -57030,29 +57245,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -57060,35 +57275,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -57096,40 +57311,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -57137,131 +57352,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -57281,29 +57496,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -57314,17 +57529,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "Ausführen"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -57434,6 +57649,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -57518,61 +57737,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -57581,13 +57800,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -57596,11 +57815,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -57608,14 +57827,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -57623,14 +57842,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -57639,14 +57858,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -57656,7 +57875,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -57665,7 +57884,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -57674,7 +57893,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -57705,7 +57924,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -57715,7 +57934,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -57723,14 +57942,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -57738,21 +57957,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -57761,7 +57980,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -57771,7 +57990,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/el.po b/weblate/el.po
index 0994eddb0f..8585074927 100644
--- a/weblate/el.po
+++ b/weblate/el.po
@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-09-25 10:27+0000\n"
 "Last-Translator: George Tsiamasiotis <gtsiam@windowslive.com>\n"
 "Language-Team: Greek <https://hosted.weblate.org/projects/godot-engine/godot-"
@@ -70,9 +70,9 @@ msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 
 #: ../../docs/index.rst:43
@@ -140,7 +140,6 @@ msgstr "Σχετικά"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -159,6 +158,7 @@ msgstr "Σχετικά"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -361,10 +361,11 @@ msgstr ""
 "επεξεργαστή."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1459,7 +1460,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1926,7 +1927,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -2001,13 +2002,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2251,8 +2252,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2276,7 +2277,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2350,7 +2351,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2364,7 +2365,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2704,6 +2705,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Σήματα"
@@ -3175,7 +3177,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3302,7 +3304,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3514,7 +3516,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3612,7 +3614,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3640,7 +3642,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -4139,7 +4141,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4196,8 +4198,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4273,7 +4275,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4370,7 +4372,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4456,14 +4458,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4573,7 +4575,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4619,7 +4621,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4659,7 +4661,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4700,9 +4702,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4790,7 +4792,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4907,7 +4909,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4955,7 +4957,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -5097,7 +5099,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5205,7 +5207,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5229,7 +5231,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5556,9 +5558,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5588,8 +5591,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5629,8 +5633,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6532,7 +6536,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6601,9 +6605,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6620,12 +6624,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6648,8 +6652,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6825,10 +6830,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6907,16 +6912,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6927,7 +6932,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6969,7 +6974,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6996,7 +7001,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -7145,7 +7150,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7160,7 +7165,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7238,7 +7243,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7265,7 +7270,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7402,9 +7407,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7473,16 +7478,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7499,14 +7504,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7537,16 +7542,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7608,7 +7613,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7638,7 +7643,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7784,7 +7789,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7814,7 +7819,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7846,7 +7851,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8281,9 +8286,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8593,7 +8598,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8673,7 +8678,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8790,12 +8795,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8847,7 +8852,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10288,7 +10293,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10668,7 +10673,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10747,7 +10752,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10773,7 +10778,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10985,9 +10990,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -11032,7 +11037,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -11078,7 +11083,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -11089,7 +11094,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11160,7 +11165,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11180,7 +11185,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19570,7 +19575,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "Εργαλεία"
 
@@ -22506,8 +22511,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22720,9 +22724,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24710,7 +24714,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25441,437 +25445,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27637,7 +27210,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27647,7 +27220,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42944,9 +42517,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42996,9 +42569,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -43052,46 +42625,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -43099,7 +42670,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -43108,7 +42679,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -43116,7 +42687,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -43126,7 +42697,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -43137,19 +42708,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -43157,13 +42728,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43171,7 +42742,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43180,7 +42751,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43194,7 +42765,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43203,7 +42774,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43211,10 +42782,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44179,6 +43750,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -47097,6 +46673,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51642,11 +51644,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51840,45 +51842,41 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -51888,29 +51886,30 @@ msgstr ""
 "`Έργα επίδειξης της Godot <https://github.com/godotengine/godot-demo-"
 "projects>`_."
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51918,131 +51917,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -52050,55 +52045,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -52109,22 +52104,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -52133,7 +52128,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -52141,11 +52136,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -52154,42 +52149,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52199,7 +52201,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52208,7 +52210,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52216,58 +52218,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54358,7 +54557,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54366,18 +54565,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54385,23 +54584,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54409,35 +54608,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54446,103 +54645,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54550,20 +54749,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54602,11 +54801,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54616,24 +54827,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54642,7 +54853,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54650,18 +54861,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54671,7 +54882,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54680,37 +54891,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54718,63 +54929,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54782,13 +54993,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54796,7 +55007,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54804,25 +55015,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54830,30 +55041,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54861,7 +55072,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54870,25 +55081,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54899,46 +55110,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54947,68 +55158,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -55016,7 +55227,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -55025,11 +55236,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -55037,114 +55248,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55211,37 +55422,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55249,61 +55460,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55323,18 +55534,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55342,11 +55553,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55354,37 +55565,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55445,27 +55656,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55473,24 +55684,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55498,29 +55696,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55528,35 +55726,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55564,40 +55762,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55605,131 +55803,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55749,29 +55947,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55782,17 +55980,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "Εκτέλεση"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55902,6 +56100,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55986,61 +56188,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -56049,13 +56251,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -56064,11 +56266,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -56076,14 +56278,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -56091,14 +56293,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -56107,14 +56309,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -56124,7 +56326,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -56133,7 +56335,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -56142,7 +56344,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56173,7 +56375,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56183,7 +56385,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56191,14 +56393,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56206,21 +56408,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56229,7 +56431,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56239,7 +56441,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/es.po b/weblate/es.po
index 6a9ad90922..debda43480 100644
--- a/weblate/es.po
+++ b/weblate/es.po
@@ -58,7 +58,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-12-04 22:23+0000\n"
 "Last-Translator: Elena G <elena.guzbla@gmail.com>\n"
 "Language-Team: Spanish <https://hosted.weblate.org/projects/godot-engine/"
@@ -124,13 +124,14 @@ msgstr ""
 "documentación, ¡ayúdanos a mejorarla haciéndonoslo saber!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Envíanos un issue o pull request en el `repositorio de GitHub <https://"
 "github.com/godotengine/godot-docs/issues>`_, ayúdanos a `traducir la "
@@ -204,7 +205,6 @@ msgstr "Acerca de"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -223,6 +223,7 @@ msgstr "Acerca de"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -424,10 +425,11 @@ msgstr ""
 "motor, desarrollar módulos C++ o plugins para el editor."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1693,7 +1695,8 @@ msgid "It can be extended (to have more functions)."
 msgstr "Se puede extender (para tener más funciones)."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+#, fuzzy
+msgid "It can be added to another node as a child."
 msgstr "Se puede agregar a otros nodos como hijos."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -2328,13 +2331,14 @@ msgstr ""
 "relaciones de propiedad."
 
 #: ../../docs/getting_started/step_by_step/instancing_continued.rst:43
+#, fuzzy
 msgid ""
 "A lot of time spent in programming games (or software in general) is on "
 "designing an architecture and fitting game components to that architecture. "
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 "Gran parte del tiempo dedicado a programar juego (o software en general) se "
@@ -2444,17 +2448,19 @@ msgstr ""
 "adicionales de forma dinámica!"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
+#, fuzzy
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 "Esto es genial, sobre todo debido a la gran cantidad de flexibilidad "
 "proporcionada, pero también hace que nuestro trabajo de apoyo a los idiomas "
 "sea más difícil."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
+#, fuzzy
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2775,9 +2781,10 @@ msgstr ""
 "opciones relevantes."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
+#, fuzzy
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 "En GDScript el propio archivo representa la clase, por lo que el campo del "
 "nombre de la clase no se puede editar."
@@ -2809,9 +2816,10 @@ msgstr ""
 "así como en la propiedad del script en el Inspector:"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
+#, fuzzy
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 "Para editar el script, pulsa cualquiera de estos botones, ambos resaltados "
@@ -2914,11 +2922,12 @@ msgstr ""
 "a activar."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:205
+#, fuzzy
 msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 "La parte superior izquierda muestra una lista de los nodos de la escena con "
 "el nombre del nodo emisor resaltado en rojo. Selecciona aquí el nodo \"Panel"
@@ -2940,9 +2949,10 @@ msgstr ""
 "de configurar la conexión."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
+#, fuzzy
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 "Y así concluye la guía sobre cómo usar la interfaz visual. Sin embargo, este "
@@ -3409,6 +3419,7 @@ msgstr "Únicamente GDScript crea variables globales para cada script nombrado."
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Señales"
@@ -4024,10 +4035,11 @@ msgstr ""
 "un buen momento para averiguar el tamaño de la ventana de juego:"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:198
+#, fuzzy
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 "Ahora podemos utilizar la función ``_process()`` para definir lo que el "
 "jugador hará. En cada frame, se llama a ``_process()``, así que lo usaremos "
@@ -4209,10 +4221,11 @@ msgstr ""
 "abreviada de arriba:"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:372
+#, fuzzy
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 "Reproduce la escena de nuevo y revisa que la animación es correcta para cada "
 "dirección. Cuando estés seguro de que el movimiento funciona correctamente, "
@@ -4495,8 +4508,9 @@ msgid "See :ref:`doc_instancing` to learn more about instancing."
 msgstr "Mira :ref:`doc_instancing` para aprender más sobre instanciación."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
+#, fuzzy
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 "Ahora agreguemos los siguientes nodos hijo a ``Main``, y nómbralos como se "
@@ -4626,8 +4640,9 @@ msgid "Main script"
 msgstr "Script Principal"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
+#, fuzzy
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 "Agrega un script a ``Main``. Al principio del script usaremos ``export "
@@ -4668,8 +4683,9 @@ msgstr ""
 "otros dos temporizadores. ``ScoreTimer`` incrementará la puntuación en 1."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
+#, fuzzy
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -5307,7 +5323,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr "Plantillas de exportación"
@@ -5382,9 +5398,10 @@ msgstr ""
 "completa de tu juego, como un `.apk` para Android o un `.exe` para Windows."
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
+#, fuzzy
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 "En las pestañas \"Recursos\" y \"Características\" puedes personalizar cómo "
 "se exporta el juego para cada plataforma. Por ahora podemos dejar esos "
@@ -5488,8 +5505,9 @@ msgstr ""
 "dispositivo."
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
+#, fuzzy
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 "A continuación, crea un almacén de claves de depuración ejecutando el "
@@ -5621,9 +5639,10 @@ msgstr ""
 "siguientes archivos:"
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
+#, fuzzy
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -5746,9 +5765,10 @@ msgid "On top of that, you can **inherit** from any scene."
 msgstr "Además, puede **heredar** desde cualquier escena."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
+#, fuzzy
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
@@ -5758,8 +5778,9 @@ msgstr ""
 "utilizando sólo código o una mezcla de las dos."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
+#, fuzzy
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -5918,9 +5939,10 @@ msgstr ""
 "estos puede incluirse como plugins de terceros."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
+#, fuzzy
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -5987,8 +6009,9 @@ msgstr ""
 "juegos, o **construir plugins y extender el editor.**"
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
+#, fuzzy
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 "Esto lleva a un sistema confiable y flexible para UI ya que lo usa el editor "
@@ -6038,11 +6061,12 @@ msgid "Design interfaces with the Control nodes"
 msgstr "Diseño de interfaces con nodos Control"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:6
+#, fuzzy
 msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -6098,11 +6122,12 @@ msgstr ""
 "<doc_ui_game_user_interface>`."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
+#, fuzzy
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 "Utiliza únicamente nodos de Control cuando diseñes tus interfaces. Tienen "
@@ -6210,7 +6235,7 @@ msgstr "TextureRect"
 #, fuzzy
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 "**TextureRect** muestra una textura o imagen dentro de una UI. Parece "
@@ -6372,12 +6397,13 @@ msgid "TextureProgress bar, two thirds filled"
 msgstr "Barra TextureProgress, dos tercios rellenados"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:143
+#, fuzzy
 msgid ""
 "**Label** prints text to the screen. You'll find all its properties in the "
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 "**Label** imprime el texto en la pantalla. Encontrará todas sus propiedades "
 "en la sección Label, en el Inspector. Escribe el texto en la propiedad "
@@ -6439,10 +6465,11 @@ msgstr ""
 "colocar y redimensionar un elemento de UI dentro de su padre."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:174
+#, fuzzy
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -6643,11 +6670,12 @@ msgid "Arrange control nodes automatically with containers"
 msgstr "Disposición automática de los nodos de control con contenedores"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:275
+#, fuzzy
 msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 "Los containers organizan automáticamente todos los nodos de Control de los "
 "hijos, incluyendo otros contenedores en filas, columnas y más. Utilízalos "
@@ -6803,9 +6831,10 @@ msgstr ""
 "automáticamente."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
+#, fuzzy
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 "El sistema de UI de Godot es complejo, y tiene mucho más que ofrecer. Para "
@@ -6835,8 +6864,9 @@ msgstr ""
 "dinero"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
+#, fuzzy
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -7274,13 +7304,15 @@ msgid "There's no space between the logo and the other UI elements"
 msgstr "No hay espacio entre el logo y los otros elementos de la UI"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:219
+#, fuzzy
 msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 "Para centrar los elementos a la derecha, usaremos un ``CenterContainer``.  "
 "Añade un nodo ``CenterContainer`` como hijo del ``HBoxContainer``. A "
@@ -7323,13 +7355,15 @@ msgstr ""
 "disposición de la UI"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:244
+#, fuzzy
 msgid ""
 "Now we grouped the menu options together, we can tell their container to "
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 "Ahora que hemos agrupado las opciones del menú, podemos decirle a su "
 "container que se expanda para que ocupe el mayor espacio vertical posible. "
@@ -7388,9 +7422,10 @@ msgstr ""
 "de Usuario de Juego (GUI) con barras y contadores de elementos."
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
+#, fuzzy
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -8709,8 +8744,9 @@ msgid "Intro"
 msgstr "Introducción"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
+#, fuzzy
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 "En este tutorial conectarás un personaje a una barra de vida y animarás la "
@@ -8793,14 +8829,15 @@ msgid "To do this, we will use **signals**."
 msgstr "Para hacer esto, usaremos **señales**."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:49
+#, fuzzy
 msgid ""
 "Signals are Godot's version of the Observer pattern. They allow us to send "
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 "Las señales son la versión de Godot del patrón Observador. Nos permiten "
@@ -8828,13 +8865,14 @@ msgstr ""
 "and `end`."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
+#, fuzzy
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 "Carga el proyecto ``start`` en Godot. En el panel ``Sistema de Archivos`` "
 "haz doble clic en LevelMockup.tscn para abrirlo. Es una maqueta de un juego "
@@ -8871,9 +8909,11 @@ msgid "The scene tree, with the GUI scene set to display its children"
 msgstr "El árbol de escena, con la escena GUI puesto para mostrar sus hijos"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
+#, fuzzy
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 "La escena GUI encapsula toda la Interfaz de Usuario del Juego. Viene con un "
 "script básico donde obtenemos la ruta a los nodos que existen dentro de la "
@@ -9136,11 +9176,12 @@ msgstr ""
 "contents.html>`_ está disponible en línea de forma gratuita."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
+#, fuzzy
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 "Con esto en mente, vamos a conectar el ``GUI`` con el ``Player``. Haz clic "
 "en el nodo ``Player`` del panel de escenas para seleccionarlo. Dirígete al "
@@ -9252,10 +9293,11 @@ msgstr ""
 "Godot escribe el método de devolución de llamada para ti y te lleva a él"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
+#, fuzzy
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 "Dentro de los paréntesis después del nombre de la función, agregue un "
 "argumento ``player_health``. Cuando el jugador emite la señal "
@@ -9263,11 +9305,12 @@ msgstr ""
 "debería verse así:"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
+#, fuzzy
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 "El motor no convierte PascalCase a snake_case, para ejemplos de C# usaremos "
 "PascalCase para nombres de métodos y camelCase para parámetros de métodos "
@@ -9284,8 +9327,9 @@ msgstr ""
 "envía su valor de salud"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
+#, fuzzy
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 "Dentro de ``_on_Player_health_changed`` llamaremos a una segunda función "
@@ -9336,9 +9380,10 @@ msgid "set the ``TextureProgress``'s ``value`` to ``new_value``"
 msgstr "establece el ``value`` de ``TextureProgress`` en ``new_value``"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
+#, fuzzy
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 "``str`` es una función incorporada que convierte cualquier valor en texto. "
@@ -9370,11 +9415,12 @@ msgid "Animate the loss of life with the Tween node"
 msgstr "Animar la pérdida de vida con el nodo Tween"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:367
+#, fuzzy
 msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -9581,7 +9627,8 @@ msgstr ""
 "atractiva."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+#, fuzzy
+msgid "The animation is smooth, but the number is broken"
 msgstr "La animación es suave pero el número está roto"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -9599,7 +9646,8 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr "Intenta jugar de nuevo para ver una bonita animación de bloques."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+#, fuzzy
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr "Gracias a redondear animated\\_health matamos dos pájaros de un tiro"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -9703,10 +9751,11 @@ msgstr ""
 "shader y modificarlo usando un color mediante `modulate`."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:611
+#, fuzzy
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 "``modulate`` recibe un valor de ``Color`` con 4 canales: rojo, verde, azul y "
 "alfa. Si obscurecemos cualquiera de los tres primeros canales la interfaz se "
@@ -9747,8 +9796,9 @@ msgstr ""
 "``Tween``:"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
+#, fuzzy
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -9922,10 +9972,11 @@ msgstr ""
 "y nombra la animación \"intro\" cuando aparezca el cuadro de diálogo."
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
+#, fuzzy
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 "Ahora que tenemos una animación, el editor de propiedades entra en modo "
 "\"edición de animación\". En este modo, aparece un icono con forma de llave "
@@ -10008,7 +10059,7 @@ msgstr "Nodos y recursos"
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 "Hasta ahora, los :ref:`Nodos <class_Node>` han sido el tipo de datos más "
@@ -10019,9 +10070,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -10044,7 +10095,7 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 "Cuando se carga un recurso desde el disco, **siempre se carga una vez**. "
@@ -10057,7 +10108,7 @@ msgstr ""
 #, fuzzy
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -10097,16 +10148,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 #, fuzzy
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr "Clic derecho en la variable permite configurar sus propiedades:"
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -10180,7 +10231,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 "Este enfoque tiene muchas ventajas. Como la función :ref:`PackedScene."
@@ -10224,7 +10275,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -10371,7 +10422,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -10402,7 +10453,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 "Los sistemas de archivos son otro tema importante en el desarrollo de "
 "motores. El sistema de archivos gestiona cómo se almacenan los recursos y "
@@ -10454,7 +10505,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 "En general, el sistema de archivos Godot evita el uso de archivos de "
@@ -11058,9 +11109,9 @@ msgstr ""
 #, fuzzy
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 "Aquí puede agregar la cantidad de scenas o scripts que quiera. Cada entrada "
 "en esta lista requiere un nombre, que es asignado como la propiedad ``name`` "
@@ -11433,12 +11484,13 @@ msgstr ""
 "editor de escenas que desees."
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:57
+#, fuzzy
 msgid ""
 "While both editors may seem similar, there are many differences below the "
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 "Aunque ambos editores pueden parecer similares, hay muchas diferencias bajo "
 "la superficie. Ambos permiten organizar el proyecto utilizando el sistema de "
@@ -11561,7 +11613,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 #, fuzzy
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -11731,12 +11783,12 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 #, fuzzy
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 "En segundo lugar, permite extraer un subárbol de escena para convertirlo en "
 "una escena propia, lo que responde a las preguntas segunda y tercera: "
@@ -11811,9 +11863,10 @@ msgstr ""
 "prefab."
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
+#, fuzzy
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -13493,10 +13546,11 @@ msgstr ""
 "los índices pueden ser negativos como en Python, para contar desde el final."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:489
+#, fuzzy
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -13959,8 +14013,9 @@ msgid "Remove ``case``"
 msgstr "Elimina ``case``"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
+#, fuzzy
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 "Elimina todos los ``break``'s. Si no quieres que la ejecución se detenga por "
@@ -14052,9 +14107,10 @@ msgstr ""
 "tanto, puedes anidarlos."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
+#, fuzzy
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 "La longitud del array se comprueba primero, tiene que tener el mismo tamaño "
 "que el patrón, de otra manera no habrá coincidencia."
@@ -14084,9 +14140,10 @@ msgstr ""
 "un patrón de constante."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
+#, fuzzy
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 "El tamaño del diccionario se comprueba primero y tiene que ser igual al del "
 "patrón, de otra manera, el patrón no coincidirá."
@@ -14352,11 +14409,12 @@ msgstr ""
 "palabra clave exportada (ver abajo)."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
+#, fuzzy
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 "Uno de los beneficios fundamentales de exportar variables miembro es poder "
 "verlas y modificarlas en el editor. De este modo los artistas y los "
@@ -14419,8 +14477,9 @@ msgid "Exporting arrays"
 msgstr "Exportando arrays"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
+#, fuzzy
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -14487,8 +14546,9 @@ msgstr ""
 "editor en scripts del editor o plugins, para validar la entrada de datos."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
+#, fuzzy
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 "Como se ha indicado previamente, los accesos *locales* *no* ejecutan setter "
@@ -14499,9 +14559,10 @@ msgid "Tool mode"
 msgstr "Modo Tool"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
+#, fuzzy
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -14595,13 +14656,14 @@ msgid "Coroutines with yield"
 msgstr "Corrutinas con yield"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1520
+#, fuzzy
 msgid ""
 "GDScript offers support for `coroutines <https://en.wikipedia.org/wiki/"
 "Coroutine>`_ via the ``yield`` built-in function. Calling ``yield()`` will "
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 "GDScript ofrece soporte para `Corrutinas <https://en.wikipedia.org/wiki/"
 "Coroutine>`_ a través de la función integrada ``yield``. Ejecutar "
@@ -14627,9 +14689,10 @@ msgid "Coroutines & signals"
 msgstr "Corrutinas y Señales"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
+#, fuzzy
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 "La fortaleza real del uso de ``yield`` aparece cuando se combina con "
@@ -25378,7 +25441,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr "¡Ejecutémoslo de nuevo! ¡Esta vez, la rotación se muestra bien!"
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "Herramientas"
 
@@ -29272,10 +29335,10 @@ msgstr ""
 "cercanos (como un personaje en un juego en tercera persona)."
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
+#, fuzzy
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 "Asegúrate de indicar una *Max Distance* de sombra de acuerdo con las "
 "necesidades de la escena. Cuanto más cerca se encuentre la distancia máxima, "
@@ -29528,9 +29591,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -31555,7 +31618,7 @@ msgstr ":ref:`String <class_String>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
 #, fuzzy
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ":ref:`Color <class_Color>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -32292,438 +32355,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-#, fuzzy
-msgid "Fragment shader"
-msgstr "Fragment Shader"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr "Uniforms"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr "Interactuar con la luz"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr "Tutorial FPS"
@@ -34564,7 +34195,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -34574,7 +34205,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -51349,9 +50980,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -51401,9 +51032,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -51458,47 +51089,45 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 #, fuzzy
 msgid "Coloring the planet"
 msgstr "Configurando el proyecto"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -51506,7 +51135,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -51515,7 +51144,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -51523,7 +51152,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -51533,7 +51162,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -51544,20 +51173,20 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 #, fuzzy
 msgid "Making an ocean"
 msgstr "Borrar una escena"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -51565,13 +51194,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -51579,7 +51208,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -51588,7 +51217,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -51602,7 +51231,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -51611,7 +51240,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -51619,10 +51248,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -52683,6 +52312,11 @@ msgstr ""
 "El valor es interpolado en una manera corregida por perspectiva. Es el modo "
 "por defecto"
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr "Uniforms"
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -55647,6 +55281,433 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+#, fuzzy
+msgid "Fragment shader"
+msgstr "Fragment Shader"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr "Interactuar con la luz"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr "Redes"
@@ -60713,11 +60774,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -60923,46 +60984,42 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 #, fuzzy
 msgid "Setting up the project"
 msgstr "Configuración de un proyecto"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr "Hay algunos requisitos previos que necesitarás:"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -60971,29 +61028,30 @@ msgstr ""
 "Si está contribuyendo a la documentación, puedes encontrar su repositorio "
 "`aquí <https://github.com/godotengine/godot-docs>`_."
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -61001,131 +61059,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr "Creación de un simple plugin"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -61133,58 +61187,58 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 #, fuzzy
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 "Después de eso declaramos una sola variable de miembro llamada "
 "``time_passed``."
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -61195,22 +61249,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -61219,7 +61273,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -61227,12 +61281,12 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 #, fuzzy
 msgid "Compiling the plugin"
 msgstr "Personalizando la presentación"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -61241,42 +61295,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -61286,7 +61347,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -61295,7 +61356,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -61303,58 +61364,256 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+#, fuzzy
+msgid "Adding properties"
+msgstr "Propiedades de los nodos"
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -63478,7 +63737,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -63486,18 +63745,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -63505,23 +63764,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -63529,35 +63788,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -63566,103 +63825,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -63670,20 +63929,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -63722,11 +63981,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -63736,24 +64007,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -63762,7 +64033,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -63770,18 +64041,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -63791,7 +64062,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -63800,37 +64071,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -63838,63 +64109,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -63902,13 +64173,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -63916,7 +64187,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -63924,25 +64195,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -63950,30 +64221,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -63981,7 +64252,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -63990,25 +64261,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -64019,46 +64290,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -64067,68 +64338,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -64136,7 +64407,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -64145,11 +64416,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -64157,114 +64428,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -64331,37 +64602,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -64369,61 +64640,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -64444,18 +64715,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -64463,11 +64734,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -64475,37 +64746,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -64566,27 +64837,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -64594,24 +64865,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -64619,31 +64877,31 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 "Release template (se utiliza al exportar con \"Debugging Enabled\" OFF)"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 "Debug template (se utiliza cuando se exporta con \"Debugging Enabled\" ON)"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -64651,35 +64909,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -64687,7 +64945,7 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
@@ -64695,34 +64953,34 @@ msgstr ""
 "Al exportar tu juego, Godot abre el APK, cambia algunas cosas dentro y añade "
 "tus archivos."
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -64730,131 +64988,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -64874,29 +65132,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -64907,17 +65165,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "Ejecutar"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -65027,6 +65285,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -65111,61 +65373,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -65174,13 +65436,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -65189,11 +65451,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -65201,14 +65463,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -65216,14 +65478,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -65232,14 +65494,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -65249,7 +65511,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -65258,7 +65520,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -65267,7 +65529,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -65298,7 +65560,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -65308,7 +65570,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -65316,7 +65578,7 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
@@ -65327,7 +65589,7 @@ msgstr ""
 "problema de seguridad, la opción ``javascript_eval`` puede usarse para "
 "compilar sin el singleton:"
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -65335,21 +65597,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -65358,7 +65620,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -65368,7 +65630,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/es_MX.po b/weblate/es_MX.po
index 62456243d5..c6ebe6cb54 100644
--- a/weblate/es_MX.po
+++ b/weblate/es_MX.po
@@ -21,7 +21,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-12-04 22:23+0000\n"
 "Last-Translator: Gato Wormius <gatowormius@gmail.com>\n"
 "Language-Team: Spanish (Mexico) <https://hosted.weblate.org/projects/godot-"
@@ -87,13 +87,14 @@ msgstr ""
 "¡Ayúdanos a crear una mejor documentación haciéndonos saber!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Enviar un problema o solicitud de extracción en el repositorio `GitHub "
 "<https://github.com/godotengine/godot-docs/issues>`_, ayúdanos a `traducir "
@@ -168,7 +169,6 @@ msgstr "Acerca de"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -187,6 +187,7 @@ msgstr "Acerca de"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -388,10 +389,11 @@ msgstr ""
 "del motor, el desarrollo de módulos C ++ o plugins de edición."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1651,7 +1653,8 @@ msgid "It can be extended (to have more functions)."
 msgstr "Se puede extender (para tener más funciones)."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+#, fuzzy
+msgid "It can be added to another node as a child."
 msgstr "Se puede agregar a otros nodos como hijos."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -2288,13 +2291,14 @@ msgstr ""
 "las relaciones de propiedad."
 
 #: ../../docs/getting_started/step_by_step/instancing_continued.rst:43
+#, fuzzy
 msgid ""
 "A lot of time spent in programming games (or software in general) is on "
 "designing an architecture and fitting game components to that architecture. "
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 "Una gran cantidad de tiempo dedicado a la programación de juegos (o software "
@@ -2407,17 +2411,19 @@ msgstr ""
 "dinámicamente!"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
+#, fuzzy
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 "Esto es excelente, en gran parte debido a la gran cantidad de flexibilidad "
 "proporcionada, pero también hace que nuestro trabajo de soporte de lenguajes "
 "sea más difícil."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
+#, fuzzy
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2739,9 +2745,10 @@ msgstr ""
 "del guión (script)."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
+#, fuzzy
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 "En GDScript, el archivo en sí representa la clase, por lo que el nombre del "
 "campo de clase no es editable."
@@ -2774,9 +2781,10 @@ msgstr ""
 "la propiedad del script bajo Inspector:"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
+#, fuzzy
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 "Para editar la secuencia de comandos (el script), seleccione cualquiera de "
@@ -2877,11 +2885,12 @@ msgstr ""
 "(representado aquí como un NodePath) y el nombre del método para activarlo."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:205
+#, fuzzy
 msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 "La sección superior izquierda muestra una lista de los nodos de su escena "
 "con el nombre del nodo emisor resaltado en rojo. Seleccione el nodo \"Panel"
@@ -2903,9 +2912,10 @@ msgstr ""
 "antes de configurar la conexión."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
+#, fuzzy
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 "Y eso concluye la guía sobre cómo usar la interfaz visual. Sin embargo, este "
@@ -3373,6 +3383,7 @@ msgstr "Solo GDScript crea variables globales para cada script con nombre."
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Señales"
@@ -4033,10 +4044,11 @@ msgstr ""
 "la ventana del juego:"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:198
+#, fuzzy
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 "Ahora podemos usar la función ``_process()``(\"_procesos()\") para definir "
 "lo que hará el jugador. ``_process()`` llama a cada fotograma, por lo que lo "
@@ -4217,10 +4229,11 @@ msgstr ""
 "booleana acortada anterior:"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:372
+#, fuzzy
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 "Corra la escena y verifique que las animaciones sean correctas en cada una "
 "de las direcciones. Cuando estés seguro de que el movimiento está "
@@ -4512,7 +4525,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -4610,7 +4623,7 @@ msgstr "Script principal"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -4638,7 +4651,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -5136,7 +5149,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -5192,8 +5205,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -5269,7 +5282,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -5366,7 +5379,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -5452,14 +5465,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -5568,7 +5581,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -5614,7 +5627,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -5654,7 +5667,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -5695,9 +5708,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -5785,7 +5798,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -5902,7 +5915,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -5950,7 +5963,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -6092,7 +6105,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -6200,7 +6213,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -6224,7 +6237,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -6551,9 +6564,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -6583,8 +6597,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -6624,8 +6639,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -7527,7 +7542,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -7596,9 +7611,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -7615,12 +7630,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -7643,8 +7658,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -7820,10 +7836,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -7902,16 +7918,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -7922,7 +7938,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -7964,7 +7980,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -7991,7 +8007,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -8140,7 +8156,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -8155,7 +8171,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -8233,7 +8249,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -8260,7 +8276,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -8397,9 +8413,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -8468,16 +8484,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -8494,14 +8510,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -8532,16 +8548,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -8603,7 +8619,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -8634,7 +8650,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -8780,7 +8796,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -8810,7 +8826,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -8842,7 +8858,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -9277,9 +9293,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -9588,7 +9604,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -9668,7 +9684,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -9785,12 +9801,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -9842,7 +9858,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -11278,7 +11294,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -11658,7 +11674,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -11737,7 +11753,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -11763,7 +11779,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -11974,9 +11990,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -12021,7 +12037,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -12067,7 +12083,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -12078,7 +12094,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -12149,7 +12165,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -12169,7 +12185,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -20555,7 +20571,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -23489,8 +23505,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -23703,9 +23718,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -25700,8 +25715,9 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
-msgstr ""
+#, fuzzy
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
+msgstr ":ref:`AnimatedSprite <class_AnimatedSprite>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
 msgid "CSG tools features"
@@ -26436,437 +26452,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -28632,7 +28217,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -28642,7 +28227,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -43940,9 +43525,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -43992,9 +43577,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -44048,47 +43633,45 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 #, fuzzy
 msgid "Coloring the planet"
 msgstr "Configurando el proyecto"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -44096,7 +43679,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -44105,7 +43688,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -44113,7 +43696,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -44123,7 +43706,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -44134,19 +43717,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -44154,13 +43737,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -44168,7 +43751,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -44177,7 +43760,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -44191,7 +43774,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -44200,7 +43783,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -44208,10 +43791,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -45176,6 +44759,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -48091,6 +47679,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -52635,11 +52649,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -52833,74 +52847,71 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 #, fuzzy
 msgid "Setting up the project"
 msgstr "Creando un nuevo proyecto"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -52908,131 +52919,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -53040,55 +53047,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -53099,22 +53106,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -53123,7 +53130,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -53131,11 +53138,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -53144,42 +53151,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -53189,7 +53203,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -53198,7 +53212,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -53206,58 +53220,256 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+#, fuzzy
+msgid "Adding properties"
+msgstr "Tiene propiedades editables."
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -55349,7 +55561,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -55357,18 +55569,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -55376,23 +55588,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -55400,35 +55612,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -55437,103 +55649,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -55541,20 +55753,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -55593,11 +55805,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -55607,24 +55831,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -55633,7 +55857,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -55641,18 +55865,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -55662,7 +55886,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -55671,37 +55895,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -55709,63 +55933,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -55773,13 +55997,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -55787,7 +56011,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -55795,25 +56019,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -55821,30 +56045,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -55852,7 +56076,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -55861,25 +56085,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -55890,46 +56114,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -55938,68 +56162,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -56007,7 +56231,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -56016,11 +56240,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -56028,114 +56252,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -56202,37 +56426,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -56240,61 +56464,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -56314,18 +56538,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -56333,11 +56557,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -56345,37 +56569,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -56436,27 +56660,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -56464,24 +56688,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -56489,29 +56700,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -56519,35 +56730,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -56555,40 +56766,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -56596,131 +56807,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -56740,29 +56951,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -56773,17 +56984,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -56893,6 +57104,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -56977,61 +57192,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -57040,13 +57255,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -57055,11 +57270,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -57067,14 +57282,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -57082,14 +57297,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -57098,14 +57313,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -57115,7 +57330,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -57124,7 +57339,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -57133,7 +57348,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -57164,7 +57379,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -57174,7 +57389,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -57182,14 +57397,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -57197,21 +57412,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -57220,7 +57435,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -57230,7 +57445,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/fa.po b/weblate/fa.po
index 797800151f..fd5eb2495a 100644
--- a/weblate/fa.po
+++ b/weblate/fa.po
@@ -12,7 +12,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-11-20 10:45+0000\n"
 "Last-Translator: Mahdi <sadisticwarlock@gmail.com>\n"
 "Language-Team: Persian <https://hosted.weblate.org/projects/godot-engine/"
@@ -75,13 +75,14 @@ msgstr ""
 "ها ما را در این امر یاری کنید!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "در `مخزن های گیت هاب <https://github.com/godotengine/godot-docs/issues>`_ یک "
 "issue ایجاد کنید یا یک pull request ثبت کنید. به ما کمک کنید تا مستندات را "
@@ -153,7 +154,6 @@ msgstr "درباره"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -172,6 +172,7 @@ msgstr "درباره"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -365,9 +366,9 @@ msgstr ""
 
 #: ../../docs/about/introduction.rst:85
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1314,7 +1315,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1781,7 +1782,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1856,13 +1857,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2106,8 +2107,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2131,7 +2132,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2205,7 +2206,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2219,7 +2220,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2559,6 +2560,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "سیگنال‌ها"
@@ -3029,7 +3031,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3155,7 +3157,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3365,7 +3367,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3463,7 +3465,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3491,7 +3493,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -3989,7 +3991,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4046,8 +4048,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4123,7 +4125,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4220,7 +4222,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4306,14 +4308,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4422,7 +4424,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4468,7 +4470,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4508,7 +4510,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4549,9 +4551,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4639,7 +4641,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4756,7 +4758,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4804,7 +4806,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4946,7 +4948,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5054,7 +5056,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5078,7 +5080,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5405,9 +5407,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5437,8 +5440,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5478,8 +5482,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6381,7 +6385,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6450,9 +6454,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6469,12 +6473,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6497,8 +6501,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6674,10 +6679,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6756,16 +6761,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6776,7 +6781,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6818,7 +6823,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6845,7 +6850,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -6994,7 +6999,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7009,7 +7014,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7087,7 +7092,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7114,7 +7119,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7251,9 +7256,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7322,16 +7327,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7348,14 +7353,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7386,16 +7391,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7457,7 +7462,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7487,7 +7492,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7633,7 +7638,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7663,7 +7668,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7695,7 +7700,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8130,9 +8135,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8442,7 +8447,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8522,7 +8527,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8639,12 +8644,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8696,7 +8701,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10134,7 +10139,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10514,7 +10519,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10593,7 +10598,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10619,7 +10624,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10830,9 +10835,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10877,7 +10882,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10923,7 +10928,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10934,7 +10939,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11005,7 +11010,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11025,7 +11030,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19414,7 +19419,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -22348,8 +22353,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22562,9 +22566,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24550,7 +24554,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25281,437 +25285,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27477,7 +27050,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27487,7 +27060,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42781,9 +42354,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42833,9 +42406,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42889,46 +42462,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42936,7 +42507,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42945,7 +42516,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42953,7 +42524,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42963,7 +42534,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -42974,19 +42545,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -42994,13 +42565,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43008,7 +42579,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43017,7 +42588,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43031,7 +42602,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43040,7 +42611,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43048,10 +42619,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44016,6 +43587,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46932,6 +46508,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51476,11 +51478,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51674,73 +51676,70 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51748,131 +51747,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51880,55 +51875,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51939,22 +51934,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51963,7 +51958,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -51971,11 +51966,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -51984,42 +51979,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52029,7 +52031,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52038,7 +52040,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52046,58 +52048,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54187,7 +54386,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54195,18 +54394,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54214,23 +54413,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54238,35 +54437,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54275,103 +54474,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54379,20 +54578,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54431,11 +54630,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54445,24 +54656,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54471,7 +54682,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54479,18 +54690,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54500,7 +54711,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54509,37 +54720,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54547,63 +54758,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54611,13 +54822,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54625,7 +54836,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54633,25 +54844,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54659,30 +54870,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54690,7 +54901,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54699,25 +54910,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54728,46 +54939,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54776,68 +54987,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54845,7 +55056,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54854,11 +55065,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54866,114 +55077,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55040,37 +55251,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55078,61 +55289,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55152,18 +55363,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55171,11 +55382,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55183,37 +55394,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55274,27 +55485,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55302,24 +55513,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55327,29 +55525,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55357,35 +55555,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55393,40 +55591,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55434,131 +55632,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55578,29 +55776,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55611,17 +55809,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55731,6 +55929,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55815,61 +56017,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55878,13 +56080,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55893,11 +56095,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55905,14 +56107,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55920,14 +56122,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55936,14 +56138,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55953,7 +56155,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55962,7 +56164,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -55971,7 +56173,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56002,7 +56204,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56012,7 +56214,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56020,14 +56222,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56035,21 +56237,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56058,7 +56260,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56068,7 +56270,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/fi.po b/weblate/fi.po
index 84e0d9a13d..fe8bb5962b 100644
--- a/weblate/fi.po
+++ b/weblate/fi.po
@@ -13,7 +13,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-11-26 14:08+0000\n"
 "Last-Translator: Tapani Niemi <tapani.niemi@kapsi.fi>\n"
 "Language-Team: Finnish <https://hosted.weblate.org/projects/godot-engine/"
@@ -77,13 +77,14 @@ msgstr ""
 "parempi kertomalla siitä meille!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Lähetä ongelma tai pull request `GitHub repositoryyn <https://github.com/"
 "godotengine/godot-docs/issues>`_, auta meitä `kääntämällä dokumentaatio "
@@ -155,7 +156,6 @@ msgstr "Tietoja"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -174,6 +174,7 @@ msgstr "Tietoja"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -370,10 +371,11 @@ msgstr ""
 "editorin liitännäisten kehittämisestä."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1623,7 +1625,8 @@ msgid "It can be extended (to have more functions)."
 msgstr "Sitä voidaan laajentaa (jotta se voi saada lisää funktioita)."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+#, fuzzy
+msgid "It can be added to another node as a child."
 msgstr "Se voidaan lisätä muiden solmujen alisolmuksi."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -2242,13 +2245,14 @@ msgstr ""
 "(joko koodista tai suoraan editorista käsin) omistajuussuhteita varten."
 
 #: ../../docs/getting_started/step_by_step/instancing_continued.rst:43
+#, fuzzy
 msgid ""
 "A lot of time spent in programming games (or software in general) is on "
 "designing an architecture and fitting game components to that architecture. "
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 "Iso osa pelien (tai ohjelmistojen ylipäänsä) ohjelmoimiseen kuluvasta ajasta "
@@ -2357,16 +2361,18 @@ msgstr ""
 "dynaamisesti!"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
+#, fuzzy
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 "Tämä on erinomaista, pääasiassa sen tarjoaman suuren joustavuuden vuoksi, "
 "mutta se tekee myös työstämme kielien tukemiseksi vaikeampaa."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
+#, fuzzy
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2682,9 +2688,10 @@ msgstr ""
 "luokan nimen ja muita oleellisia asetuksia."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
+#, fuzzy
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 "GDScriptissä tiedosto itse edustaa luokkaa, joten luokan nimi ei ole "
 "muokattavissa."
@@ -2714,9 +2721,10 @@ msgstr ""
 "Script-ominaisuutena Tarkastelussa:"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
+#, fuzzy
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 "Skriptin muokkaamiseksi käytä jompaa kumpaa näistä painikkeista, jotka on "
@@ -2817,11 +2825,12 @@ msgstr ""
 "to Node) ja laukaistavan metodin nimi."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:205
+#, fuzzy
 msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 "Ylhäällä vasemmalla oleva osio näyttää luettelon kaikista skenesi solmuista, "
 "lähettävän solmun nimi punaisella korostettuna. Valitse siitä \"Panel\" "
@@ -2841,9 +2850,10 @@ msgstr ""
 "on päällä, editori luo funktion sinulle ennen kytkennän asettamista."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
+#, fuzzy
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 "Ja siihen päättyy opastus visuaalisesta kytkennän luonnista. Tämä on "
@@ -3304,6 +3314,7 @@ msgstr "Vain GDScript luo globaaleja muuttujia kullekin nimetylle skriptille."
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Signaalit"
@@ -3868,10 +3879,11 @@ msgstr ""
 "hyvä hetki hakea peli-ikkunan koko:"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:198
+#, fuzzy
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 "Nyt voimme käyttää ``_process()`` funktiota määrittelemään mitä pelaaja "
 "tekee. ``_process()`` funktiota kutsutaan jokaisella ruudunpäivityksellä, "
@@ -4047,10 +4059,11 @@ msgstr ""
 "sijoituksiin verrattuna:"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:372
+#, fuzzy
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 "Pelaa skene uudelleen ja tarkista, että animaatiot toimivat oikein kuhunkin "
 "suuntaan. Kun olet varma, että liikkuminen toimii oikein, lisää tämä rivi "
@@ -4328,8 +4341,9 @@ msgid "See :ref:`doc_instancing` to learn more about instancing."
 msgstr "Katso :ref:`doc_instancing` oppiaksesi enemmän ilmentymistä."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
+#, fuzzy
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 "Lisää nyt seuraavat solmut ``Main`` solmun alisolmuiksi ja nimeä ne "
@@ -4456,8 +4470,9 @@ msgid "Main script"
 msgstr "Pääskripti"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
+#, fuzzy
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 "Lisää skripti ``Main`` solmulle. Skriptin alussa käytämme ``export "
@@ -4498,8 +4513,9 @@ msgstr ""
 "ajastinta. ``ScoreTimer`` kasvattaa pistelaskuria yhdellä."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
+#, fuzzy
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -5136,7 +5152,7 @@ msgstr "Tässä koko skripti pelaajalle, muutokset kommenteihin merkittynä:"
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr "Vientimallit"
@@ -5208,9 +5224,10 @@ msgstr ""
 "pelistäsi, kuten esimerkiksi `.apk` Androidille tai `.exe` Windowsille."
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
+#, fuzzy
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 "\"Resurssit\" ja \"Ominaisuudet\" välilehdillä voit räätälöidä pelisi "
 "viennin kullekin alustalle. Voimme jättää nuo asetukset rauhaan toistaiseksi."
@@ -5312,8 +5329,9 @@ msgstr ""
 "komentorivityökalun, jota Godot käyttää keskustellakseen laitteesi kanssa."
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
+#, fuzzy
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 "Seuraavaksi, luo \"debug keystore\" suorittamalla seuraava komento "
@@ -5439,9 +5457,10 @@ msgid ""
 msgstr "Kun vienti on valmis, saat seuraavat tiedostot sisältävän kansion:"
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
+#, fuzzy
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -5541,14 +5560,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -5657,7 +5676,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -5703,7 +5722,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -5743,7 +5762,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -5784,9 +5803,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -5874,7 +5893,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -5991,7 +6010,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -6039,7 +6058,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -6181,7 +6200,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -6289,7 +6308,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -6313,7 +6332,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -6640,9 +6659,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -6672,8 +6692,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -6713,8 +6734,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -7616,7 +7637,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -7685,9 +7706,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -7708,12 +7729,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -7736,8 +7757,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -7913,10 +7935,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -7995,16 +8017,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -8015,7 +8037,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -8057,7 +8079,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -8084,7 +8106,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -8233,7 +8255,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -8248,7 +8270,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -8326,7 +8348,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -8353,7 +8375,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -8490,9 +8512,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -8561,16 +8583,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -8587,14 +8609,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -8625,16 +8647,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -8696,7 +8718,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -8727,7 +8749,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -8873,7 +8895,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -8903,7 +8925,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -8935,7 +8957,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -9370,9 +9392,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -9689,12 +9711,13 @@ msgstr ""
 "puolelle skene-editoria."
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:57
+#, fuzzy
 msgid ""
 "While both editors may seem similar, there are many differences below the "
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 "Vaikka editorit vaikuttavat samanlaisilta, pinnan alla niillä on monia "
 "eroavaisuuksia. Molemmat antavat sinun organisoida projektin "
@@ -9796,7 +9819,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -9913,12 +9936,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -9970,7 +9993,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -11406,7 +11429,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -11786,7 +11809,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -11865,7 +11888,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -11891,7 +11914,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -12102,9 +12125,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -12149,7 +12172,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -12195,7 +12218,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -12206,7 +12229,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -12277,7 +12300,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -12297,7 +12320,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -20742,7 +20765,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "Työkalut"
 
@@ -23676,8 +23699,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -23890,9 +23912,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -25879,8 +25901,9 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
-msgstr ""
+#, fuzzy
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
+msgstr ":ref:`AnimatedSprite <class_AnimatedSprite>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
 msgid "CSG tools features"
@@ -26613,437 +26636,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -28809,7 +28401,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -28819,7 +28411,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -44118,9 +43710,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -44170,9 +43762,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -44226,46 +43818,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr "Planeetan värjäys"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -44273,7 +43863,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -44282,7 +43872,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -44290,7 +43880,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -44300,7 +43890,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -44311,19 +43901,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -44331,13 +43921,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -44345,7 +43935,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -44354,7 +43944,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -44368,7 +43958,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -44377,7 +43967,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -44385,10 +43975,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -45353,6 +44943,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -48268,6 +47863,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -52813,11 +52834,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -53011,74 +53032,71 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr "Projektin perustus"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 "kopio `godot-cpp säilöstä <https://github.com/godotengine/godot-docs>`_."
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -53086,131 +53104,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -53218,55 +53232,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -53277,22 +53291,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -53301,7 +53315,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -53309,11 +53323,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -53322,42 +53336,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -53367,7 +53388,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -53376,7 +53397,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -53384,58 +53405,256 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+#, fuzzy
+msgid "Adding properties"
+msgstr "Sillä on muokattavia ominaisuuksia."
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -55526,7 +55745,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -55534,18 +55753,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -55553,23 +55772,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -55577,35 +55796,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -55614,103 +55833,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -55718,20 +55937,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -55770,11 +55989,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -55784,24 +56015,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -55810,7 +56041,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -55818,18 +56049,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -55839,7 +56070,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -55848,37 +56079,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -55886,63 +56117,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -55950,13 +56181,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -55964,7 +56195,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -55972,25 +56203,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -55998,30 +56229,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -56029,7 +56260,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -56038,25 +56269,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -56067,46 +56298,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -56115,68 +56346,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -56184,7 +56415,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -56193,11 +56424,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -56205,114 +56436,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -56379,37 +56610,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -56417,61 +56648,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -56491,18 +56722,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -56510,11 +56741,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -56522,37 +56753,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -56613,27 +56844,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -56641,24 +56872,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -56666,29 +56884,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -56696,35 +56914,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -56732,40 +56950,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -56773,131 +56991,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -56917,29 +57135,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -56950,17 +57168,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "Suorita"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -57070,6 +57288,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -57154,61 +57376,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -57217,13 +57439,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -57232,11 +57454,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -57244,14 +57466,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -57259,14 +57481,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -57275,14 +57497,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -57292,7 +57514,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -57301,7 +57523,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -57310,7 +57532,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -57341,7 +57563,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -57351,7 +57573,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -57359,14 +57581,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -57374,21 +57596,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -57397,7 +57619,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -57407,7 +57629,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/fil.po b/weblate/fil.po
index 5da1adefcf..937615e773 100644
--- a/weblate/fil.po
+++ b/weblate/fil.po
@@ -9,7 +9,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-05-15 01:36+0000\n"
 "Last-Translator: Daris C. Mondigo <mondigodc@gmail.com>\n"
 "Language-Team: Filipino <https://hosted.weblate.org/projects/godot-engine/"
@@ -63,9 +63,9 @@ msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 
 #: ../../docs/index.rst:43
@@ -131,7 +131,6 @@ msgstr ""
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -150,6 +149,7 @@ msgstr ""
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -290,9 +290,9 @@ msgstr ""
 
 #: ../../docs/about/introduction.rst:85
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1233,7 +1233,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1700,7 +1700,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1775,13 +1775,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2025,8 +2025,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2050,7 +2050,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2124,7 +2124,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2138,7 +2138,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2478,6 +2478,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr ""
@@ -2948,7 +2949,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3074,7 +3075,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3283,7 +3284,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3381,7 +3382,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3409,7 +3410,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -3907,7 +3908,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -3963,8 +3964,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4040,7 +4041,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4137,7 +4138,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4223,14 +4224,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4339,7 +4340,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4385,7 +4386,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4425,7 +4426,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4466,9 +4467,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4556,7 +4557,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4673,7 +4674,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4721,7 +4722,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4863,7 +4864,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -4971,7 +4972,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -4995,7 +4996,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5322,9 +5323,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5354,8 +5356,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5395,8 +5398,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6298,7 +6301,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6367,9 +6370,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6386,12 +6389,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6414,8 +6417,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6591,10 +6595,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6673,16 +6677,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6693,7 +6697,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6735,7 +6739,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6762,7 +6766,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -6911,7 +6915,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -6926,7 +6930,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7004,7 +7008,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7031,7 +7035,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7168,9 +7172,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7239,16 +7243,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7265,14 +7269,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7303,16 +7307,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7374,7 +7378,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7404,7 +7408,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7550,7 +7554,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7580,7 +7584,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7612,7 +7616,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8047,9 +8051,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8358,7 +8362,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8438,7 +8442,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8555,12 +8559,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8612,7 +8616,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10048,7 +10052,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10428,7 +10432,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10507,7 +10511,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10533,7 +10537,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10744,9 +10748,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10791,7 +10795,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10837,7 +10841,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10848,7 +10852,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -10919,7 +10923,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -10939,7 +10943,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19312,7 +19316,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -22246,8 +22250,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22460,9 +22463,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24447,7 +24450,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25178,437 +25181,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27374,7 +26946,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27384,7 +26956,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42677,9 +42249,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42729,9 +42301,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42785,46 +42357,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42832,7 +42402,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42841,7 +42411,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42849,7 +42419,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42859,7 +42429,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -42870,19 +42440,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -42890,13 +42460,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -42904,7 +42474,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -42913,7 +42483,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -42927,7 +42497,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -42936,7 +42506,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -42944,10 +42514,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -43912,6 +43482,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46827,6 +46402,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51371,11 +51372,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51569,73 +51570,70 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51643,131 +51641,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51775,55 +51769,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51834,22 +51828,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51858,7 +51852,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -51866,11 +51860,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -51879,42 +51873,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -51924,7 +51925,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -51933,7 +51934,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -51941,58 +51942,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54082,7 +54280,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54090,18 +54288,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54109,23 +54307,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54133,35 +54331,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54170,103 +54368,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54274,20 +54472,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54326,11 +54524,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54340,24 +54550,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54366,7 +54576,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54374,18 +54584,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54395,7 +54605,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54404,37 +54614,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54442,63 +54652,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54506,13 +54716,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54520,7 +54730,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54528,25 +54738,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54554,30 +54764,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54585,7 +54795,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54594,25 +54804,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54623,46 +54833,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54671,68 +54881,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54740,7 +54950,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54749,11 +54959,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54761,114 +54971,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -54935,37 +55145,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -54973,61 +55183,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55047,18 +55257,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55066,11 +55276,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55078,37 +55288,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55169,27 +55379,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55197,24 +55407,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55222,29 +55419,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55252,35 +55449,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55288,40 +55485,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55329,131 +55526,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55473,29 +55670,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55506,17 +55703,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55626,6 +55823,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55710,61 +55911,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55773,13 +55974,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55788,11 +55989,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55800,14 +56001,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55815,14 +56016,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55831,14 +56032,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55848,7 +56049,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55857,7 +56058,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -55866,7 +56067,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -55897,7 +56098,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -55907,7 +56108,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -55915,14 +56116,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -55930,21 +56131,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -55953,7 +56154,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -55963,7 +56164,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/fr.po b/weblate/fr.po
index aedccd89e8..57ad9d6dba 100644
--- a/weblate/fr.po
+++ b/weblate/fr.po
@@ -63,7 +63,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: French (Godot Engine)\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-12-03 06:42+0000\n"
 "Last-Translator: Rémi Bintein <reminus5@hotmail.fr>\n"
 "Language-Team: French <https://hosted.weblate.org/projects/godot-engine/"
@@ -130,13 +130,14 @@ msgstr ""
 "en nous le faisant savoir !"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Ouvrez un rapport de bug ou une *pull request* sur le dépôt `GitHub <https://"
 "github.com/godotengine/godot-docs/issues>`_, aidez nous à `traduire la "
@@ -209,7 +210,6 @@ msgstr "À propos"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -228,6 +228,7 @@ msgstr "À propos"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -428,10 +429,11 @@ msgstr ""
 "l’éditeur."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1706,7 +1708,8 @@ msgid "It can be extended (to have more functions)."
 msgstr "Il peut être étendu (pour avoir plus de fonctions)."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+#, fuzzy
+msgid "It can be added to another node as a child."
 msgstr "Il peut être ajouté à d'autres nœuds en tant qu'enfant."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -2351,13 +2354,14 @@ msgstr ""
 "dans l'éditeur) pour les relations de possession."
 
 #: ../../docs/getting_started/step_by_step/instancing_continued.rst:43
+#, fuzzy
 msgid ""
 "A lot of time spent in programming games (or software in general) is on "
 "designing an architecture and fitting game components to that architecture. "
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 "Beaucoup de temps passé à programmer des jeux (ou des logiciels en général) "
@@ -2473,16 +2477,18 @@ msgstr ""
 "supplémentaires !"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
+#, fuzzy
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 "Ceci est formidable, surtout en raison de la grande flexibilité offerte, "
 "mais cela rend aussi notre travail de support des langages plus difficile."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
+#, fuzzy
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2807,9 +2813,10 @@ msgstr ""
 "d'autres options."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
+#, fuzzy
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 "Dans GDScript, le fichier lui-même représente la classe, de sorte que le "
 "champ du nom de la classe n'est pas modifiable."
@@ -2841,9 +2848,10 @@ msgstr ""
 "dans la propriété script dans l'Inspecteur :"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
+#, fuzzy
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 "Pour éditer le script, sélectionnez l'un ou l'autre de ces boutons, qui sont "
@@ -2945,11 +2953,12 @@ msgstr ""
 "déclencher."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:205
+#, fuzzy
 msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 "La section en haut à gauche affiche une liste des noeuds de votre scène avec "
 "le nom du noeud émetteur mis en évidence en rouge. Sélectionnez ici le noeud "
@@ -2971,9 +2980,10 @@ msgstr ""
 "mettre en place la connexion."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
+#, fuzzy
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 "Ainsi se conclut notre guide sur l'utilisation de l'interface visuelle. "
@@ -3448,6 +3458,7 @@ msgstr "Seul GDScript crée des variables globales pour chaque script nommé."
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Signaux"
@@ -4123,10 +4134,11 @@ msgstr ""
 "scène, ce qui est un bon moment pour trouver la taille de la fenêtre de jeu :"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:198
+#, fuzzy
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 "Maintenant nous pouvons utiliser la fonction ``_process()`` pour définir ce "
 "que le joueur va faire. ``_process()`` est appelée à chaque image, nous "
@@ -4308,10 +4320,11 @@ msgstr ""
 "booléenne raccourcie ci-dessus :"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:372
+#, fuzzy
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 "Relancez la scène et vérifiez que les animations sont correctes dans chacune "
 "des directions. Lorsque vous êtes sûr que le mouvement fonctionne "
@@ -4596,8 +4609,9 @@ msgstr ""
 "l'instanciation."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
+#, fuzzy
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 "Ajoutez maintenant les nœuds suivants en tant qu'enfants de ``Main``, et "
@@ -4727,8 +4741,9 @@ msgid "Main script"
 msgstr "Script principal"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
+#, fuzzy
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 "Ajoutez un script à ``Main``. Au début du script nous utilisons ``export "
@@ -4770,8 +4785,9 @@ msgstr ""
 "les deux autres timers. ``ScoreTimer`` incrémentera le score de 1."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
+#, fuzzy
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -5420,7 +5436,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr "Exporter des modèles"
@@ -5495,9 +5511,10 @@ msgstr ""
 "de votre jeu, comme un `.apk` pour Android ou un `.exe` pour Windows."
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
+#, fuzzy
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 "Dans les onglets \"Ressources\" et \"Fonctionnalités\", vous pouvez "
 "personnaliser la manière dont le jeu est exporté pour chaque plate-forme. "
@@ -5608,8 +5625,9 @@ msgstr ""
 "communiquer avec votre appareil."
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
+#, fuzzy
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 "Créez ensuite une keystore de débogage en exécutant la commande suivante sur "
@@ -5743,9 +5761,10 @@ msgstr ""
 "ceci :"
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
+#, fuzzy
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -5871,9 +5890,10 @@ msgid "On top of that, you can **inherit** from any scene."
 msgstr "En plus de cela, vous pouvez **hériter** de n'importe quelle scène."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
+#, fuzzy
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
@@ -5884,8 +5904,9 @@ msgstr ""
 "en mélangeant et en faisant correspondre les deux."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
+#, fuzzy
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -6050,9 +6071,10 @@ msgstr ""
 "place."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
+#, fuzzy
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -6120,8 +6142,9 @@ msgstr ""
 "l'éditeur.**"
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
+#, fuzzy
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 "Cela conduit à un système d'interface utilisateur fiable et flexible car "
@@ -6171,11 +6194,12 @@ msgid "Design interfaces with the Control nodes"
 msgstr "Conception d'interfaces avec les nœuds Control"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:6
+#, fuzzy
 msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -6234,11 +6258,12 @@ msgstr ""
 "Godot <doc_ui_game_user_interface_user_interface>`."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
+#, fuzzy
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 "Utilisez uniquement les nœuds Control lorsque vous concevez vos interfaces. "
@@ -6347,7 +6372,7 @@ msgstr "TextureRect"
 #, fuzzy
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 "**TextureRect** affiche une texture ou une image à l'intérieur d'une "
@@ -6511,12 +6536,13 @@ msgid "TextureProgress bar, two thirds filled"
 msgstr "Barre TextureProgress, remplie aux deux tiers"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:143
+#, fuzzy
 msgid ""
 "**Label** prints text to the screen. You'll find all its properties in the "
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 "Un **Label** affiche du texte à l'écran. Vous trouverez toutes ses "
 "propriétés dans la section Label, dans l'Inspecteur. Ecrivez le texte dans "
@@ -6582,10 +6608,11 @@ msgstr ""
 "placer et redimensionner un élément d'interface utilisateur dans son parent."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:174
+#, fuzzy
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -6798,11 +6825,12 @@ msgid "Arrange control nodes automatically with containers"
 msgstr "Arrangez automatiquement les nœuds de contrôle avec les conteneurs"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:275
+#, fuzzy
 msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 "Les conteneurs rangent automatiquement tous les nœuds Control enfants, y "
 "compris les autres conteneurs en rangées, colonnes et plus encore. Utilisez-"
@@ -6970,9 +6998,10 @@ msgstr ""
 "automatiquement."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
+#, fuzzy
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 "Le système d'interface utilisatuer de Godot est complexe et a beaucoup plus "
@@ -7004,8 +7033,9 @@ msgstr ""
 "d'énergie, une bombe et des compteurs d'argent"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
+#, fuzzy
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -7454,13 +7484,15 @@ msgid "There's no space between the logo and the other UI elements"
 msgstr "Il n'y a pas d'espace entre le logo et les autres élements de l'UI"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:219
+#, fuzzy
 msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 "Pour centrer les caractères à droite, nous utiliserons un "
 "``CenterContainer``.  Ajoutez un noeud ``CenterContainer`` comme enfant du "
@@ -7505,13 +7537,15 @@ msgstr ""
 "disposition de l'interface utilisateur"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:244
+#, fuzzy
 msgid ""
 "Now we grouped the menu options together, we can tell their container to "
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 "Maintenant que nous avons regroupé les options de menu ensembles, nous "
 "pouvons étendre le conteneur pour qu'il prenne toute l'espace vertical "
@@ -7572,9 +7606,10 @@ msgstr ""
 "d'objets."
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
+#, fuzzy
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -8959,8 +8994,9 @@ msgid "Intro"
 msgstr "Introduction"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
+#, fuzzy
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 "Dans ce tutoriel, vous allez connecter un personnage à une barre de vie et "
@@ -9047,14 +9083,15 @@ msgid "To do this, we will use **signals**."
 msgstr "Pour ce faire, nous utiliserons des **signaux**."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:49
+#, fuzzy
 msgid ""
 "Signals are Godot's version of the Observer pattern. They allow us to send "
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 "Les signaux sont la version Godot du patron de conception Observateur. Ils "
@@ -9083,13 +9120,14 @@ msgstr ""
 "deux dossiers : `start` et `end`."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
+#, fuzzy
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 "Charger le projet ``start`` dans Godot. Dans le dock ``FileSystem``, double-"
 "cliquez sur LevelMockup.tscn pour l'ouvrir. C'est une maquette de jeu de "
@@ -9130,8 +9168,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 #, fuzzy
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 "La scène de l'interface graphique contient tous les éléments de l'interface "
 "graphique. Elle est attaché à un script permettant de récupérer les "
@@ -9417,11 +9456,12 @@ msgstr ""
 "gratuitement."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
+#, fuzzy
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 "Dans cette optique, connectons le ``GUI`` à ``Player``. Cliquez sur le nœud "
 "``Player`` dans le dock de scène pour le sélectionner. Dirigez-vous vers "
@@ -9541,8 +9581,8 @@ msgstr "Godot écrit la méthode de rappel pour vous et vous y emmène"
 #, fuzzy
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 "Entre les parenthèses après le nom de notre méthode, ajouter un argument "
 "``player_health``. Quand le signal ``health_changed`` sera émis, il enverra "
@@ -9550,11 +9590,12 @@ msgstr ""
 "Votre code devrait ressembler à :"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
+#, fuzzy
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 "Le moteur ne convertit pas PascalCase en snake_case, pour les exemples C# "
 "nous utiliserons PascalCase pour les noms de méthode et camelCase pour les "
@@ -9574,7 +9615,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 #, fuzzy
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 "Dans la méthode ``_on_Player_health_changed``, appelons une seconde fonction "
@@ -9638,7 +9679,7 @@ msgstr ""
 #, fuzzy
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 "``str`` est une fonction qui converti une valeur en texte. La propriété "
@@ -9676,7 +9717,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -9906,7 +9947,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
 #, fuzzy
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr "L'animation est fluide mais le nombre est cassé"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -9928,7 +9969,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
 #, fuzzy
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr "En arrondissant animated\\_health, on a fait d'une pierre deux coups"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -10042,10 +10083,11 @@ msgstr ""
 "shader, et de le modifier en utilisant une couleur avec `modulate`."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:611
+#, fuzzy
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 "``modulate`` prend une valeur ``Color`` avec 4 canaux : rouge, vert, bleu et "
 "alpha. Si vous assombrissons n'importe lequel des trois premiers canaux, "
@@ -10087,7 +10129,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 #, fuzzy
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -10280,9 +10322,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 #, fuzzy
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 "Maintenant que nous avons une animation, l'éditeur de propriétés entre en "
 "mode \"édition d'animation\". Dans ce mode, une icône clé apparaît à côté de "
@@ -10371,7 +10413,7 @@ msgstr "Nœuds et ressources"
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 "Jusqu'à présent, les :ref:`Nœuds <class_Node>` ont été le type de donnée le "
@@ -10381,11 +10423,12 @@ msgstr ""
 "<class_Resource>`."
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
+#, fuzzy
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 "Les *nœuds* vous offrent des fonctionnalités: ils dessinent des sprites, des "
 "modèles 3D, simulent des propriétés physiques, organisent une interface "
@@ -10413,7 +10456,7 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 "Quand une ressource est chargée depuis le disque dur, **elle est toujours "
@@ -10427,7 +10470,7 @@ msgstr ""
 #, fuzzy
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -10474,17 +10517,18 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 #, fuzzy
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 "Cliquer droit sur la variable vous permet de configurer ses propriétés :"
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
+#, fuzzy
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 "La propriété chemin nous indique d'où provient la ressource. Dans ce cas, "
 "elle provient d'une image PNG appelée ``robi.png``. Lorsque la ressource "
@@ -10577,7 +10621,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 "Cette approche présente plusieurs avantages. Comme la fonction :ref:"
@@ -10626,8 +10670,9 @@ msgstr ""
 "mémoire de comptage de références du type Référence."
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
+#, fuzzy
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -10847,7 +10892,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -10888,7 +10933,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 "Le système de fichier est également un des derniers sujets du développement "
 "du moteur. Le système de fichier gère la façon dont les assets sont stockés "
@@ -10940,7 +10985,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 "En général, le système de fichier de Godot évite d'utiliser des fichiers de "
@@ -11573,9 +11618,9 @@ msgstr ""
 #, fuzzy
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 "Ici, vous pouvez ajouter un nombre quelconque de scènes ou de scripts. "
 "Chaque entrée de la liste nécessite un nom, lequel lui étant attribué en "
@@ -11952,12 +11997,13 @@ msgstr ""
 "souhaité de l'éditeur de scène."
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:57
+#, fuzzy
 msgid ""
 "While both editors may seem similar, there are many differences below the "
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 "Bien que les deux éditeurs puissent sembler similaires, il existe de "
 "nombreuses différences sous la surface. Les deux vous permettent d'organiser "
@@ -12081,7 +12127,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 #, fuzzy
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -12254,12 +12300,12 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 #, fuzzy
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 "Deuxièmement, il permet d'extraire une sous-arborescence de scène pour en "
 "faire une scène à part entière, qui répond aux deuxième et troisième "
@@ -12335,9 +12381,10 @@ msgstr ""
 "que celles définies par le préfabriqué."
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
+#, fuzzy
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -14060,7 +14107,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -14537,8 +14584,9 @@ msgid "Remove ``case``"
 msgstr "Enlever ``case``"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
+#, fuzzy
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 "Enlevez tous les ``break``. Si vous ne voulez pas ``break`` par défaut, vous "
@@ -14636,9 +14684,10 @@ msgstr ""
 "une expression en soi, de sorte que vous pouvez les imbriquer."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
+#, fuzzy
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 "La longueur du tableau est d'abord testée, elle doit être de la même taille "
 "que l'expression, sinon cette dernière ne correspond pas."
@@ -14668,9 +14717,10 @@ msgstr ""
 "une expression constante."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
+#, fuzzy
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 "La taille du dictionnaire est d'abord testée, elle doit être de la même "
 "taille que l'expression, sinon l'expression ne correspond pas."
@@ -14951,11 +15001,12 @@ msgstr ""
 "d'exportation (voir ci-dessous)."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
+#, fuzzy
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 "L'un des avantages fondamentaux de l'exportation des variables membres est "
 "de les rendre visibles et modifiables dans l'éditeur. De cette façon, les "
@@ -15021,8 +15072,9 @@ msgid "Exporting arrays"
 msgstr "Exportation de tableaux"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
+#, fuzzy
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -15089,8 +15141,9 @@ msgstr ""
 "valider les entrées."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
+#, fuzzy
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 "L'accès dit *local* ne déclenchera *pas* le setter et le getter. En voici "
@@ -15101,9 +15154,10 @@ msgid "Tool mode"
 msgstr "Mode outil"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
+#, fuzzy
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -15203,13 +15257,14 @@ msgid "Coroutines with yield"
 msgstr "Coroutines et signaux"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1520
+#, fuzzy
 msgid ""
 "GDScript offers support for `coroutines <https://en.wikipedia.org/wiki/"
 "Coroutine>`_ via the ``yield`` built-in function. Calling ``yield()`` will "
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 "GDScript offre un support pour les `coroutines <https://fr.wikipedia.org/"
 "wiki/Coroutine>`_ via la fonction intégrée ``yield``. L'appel de ``yield()`` "
@@ -15236,9 +15291,10 @@ msgid "Coroutines & signals"
 msgstr "Coroutines et signaux"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
+#, fuzzy
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 "La force réelle de l'utilisation du ``yield`` est lorsqu'il est combiné avec "
@@ -26258,7 +26314,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr "Allons-y encore ! Cette fois, la rotation s'opère correctement !"
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "Outils"
 
@@ -29503,8 +29559,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -29719,9 +29774,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -31728,7 +31783,7 @@ msgstr ":ref:`String <class_String>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
 #, fuzzy
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ":ref:`Color <class_Color>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -32466,437 +32521,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr "Jeu à la première personne"
@@ -34664,7 +34288,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -34674,7 +34298,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -50012,9 +49636,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -50064,9 +49688,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -50121,47 +49745,45 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 #, fuzzy
 msgid "Coloring the planet"
 msgstr "Configurer le projet"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -50169,7 +49791,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -50178,7 +49800,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -50186,7 +49808,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -50196,7 +49818,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -50207,19 +49829,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -50227,13 +49849,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -50241,7 +49863,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -50250,7 +49872,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -50264,7 +49886,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -50273,7 +49895,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -50281,10 +49903,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -51253,6 +50875,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -54193,6 +53820,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr "Réseau"
@@ -58753,11 +58806,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr "Compilation"
 
@@ -58952,47 +59005,43 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 #, fuzzy
 msgid "Setting up the project"
 msgstr "Créer un nouveau projet"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 #, fuzzy
 msgid "There are a few prerequisites you'll need:"
 msgstr "Il y a cependant quelques différences :"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -59002,29 +59051,30 @@ msgstr ""
 "aux différents `projets de démonstration de Godot <https://github.com/"
 "godotengine/godot-demo-projects>`_."
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -59032,132 +59082,128 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 #, fuzzy
 msgid "Creating a simple plugin"
 msgstr "Création d'un script C#"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -59165,57 +59211,57 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 #, fuzzy
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 "Commencez par déclarer les variables membres dont cet objet aura besoin :"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -59226,22 +59272,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -59250,7 +59296,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -59258,12 +59304,12 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 #, fuzzy
 msgid "Compiling the plugin"
 msgstr "Compilation"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -59272,42 +59318,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -59317,7 +59370,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -59326,7 +59379,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -59334,58 +59387,256 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+#, fuzzy
+msgid "Adding properties"
+msgstr "Propriétés d’un nœud"
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -61485,7 +61736,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -61493,18 +61744,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -61512,23 +61763,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -61536,35 +61787,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -61573,103 +61824,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -61677,20 +61928,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -61729,11 +61980,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -61743,24 +62006,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -61769,7 +62032,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -61777,18 +62040,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -61798,7 +62061,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -61807,37 +62070,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -61845,63 +62108,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -61909,13 +62172,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -61923,7 +62186,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -61931,25 +62194,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -61957,30 +62220,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -61988,7 +62251,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -61997,25 +62260,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -62026,46 +62289,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -62074,68 +62337,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -62143,7 +62406,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -62152,11 +62415,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -62164,114 +62427,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -62338,37 +62601,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -62376,61 +62639,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -62451,18 +62714,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -62470,11 +62733,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -62482,37 +62745,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -62573,27 +62836,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -62601,24 +62864,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -62626,29 +62876,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -62656,35 +62906,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -62692,40 +62942,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -62733,131 +62983,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -62877,29 +63127,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -62910,17 +63160,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "Lancer"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -63030,6 +63280,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -63114,61 +63368,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -63177,13 +63431,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -63192,11 +63446,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -63204,14 +63458,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -63219,14 +63473,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -63235,14 +63489,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -63252,7 +63506,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -63261,7 +63515,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -63270,7 +63524,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -63301,7 +63555,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -63311,7 +63565,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -63319,14 +63573,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -63334,21 +63588,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -63357,7 +63611,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -63367,7 +63621,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/he.po b/weblate/he.po
index 6dab443816..afa92d3673 100644
--- a/weblate/he.po
+++ b/weblate/he.po
@@ -9,7 +9,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-04-20 14:38+0000\n"
 "Last-Translator: Yaron Shahrabani <sh.yaron@gmail.com>\n"
 "Language-Team: Hebrew <https://hosted.weblate.org/projects/godot-engine/"
@@ -63,9 +63,9 @@ msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 
 #: ../../docs/index.rst:43
@@ -131,7 +131,6 @@ msgstr "על אודות"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -150,6 +149,7 @@ msgstr "על אודות"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -328,9 +328,9 @@ msgstr ""
 
 #: ../../docs/about/introduction.rst:85
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1290,7 +1290,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1757,7 +1757,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1832,13 +1832,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2082,8 +2082,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2107,7 +2107,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2181,7 +2181,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2195,7 +2195,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2535,6 +2535,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "אותות"
@@ -3007,7 +3008,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3134,7 +3135,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3345,7 +3346,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3443,7 +3444,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3471,7 +3472,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -3969,7 +3970,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4026,8 +4027,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4103,7 +4104,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4200,7 +4201,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4286,14 +4287,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4402,7 +4403,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4448,7 +4449,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4488,7 +4489,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4529,9 +4530,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4619,7 +4620,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4736,7 +4737,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4784,7 +4785,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4926,7 +4927,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5034,7 +5035,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5058,7 +5059,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5385,9 +5386,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5417,8 +5419,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5458,8 +5461,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6361,7 +6364,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6430,9 +6433,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6449,12 +6452,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6477,8 +6480,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6654,10 +6658,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6736,16 +6740,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6756,7 +6760,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6798,7 +6802,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6825,7 +6829,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -6974,7 +6978,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -6989,7 +6993,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7067,7 +7071,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7094,7 +7098,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7231,9 +7235,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7302,16 +7306,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7328,14 +7332,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7366,16 +7370,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7437,7 +7441,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7467,7 +7471,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7613,7 +7617,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7643,7 +7647,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7675,7 +7679,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8110,9 +8114,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8423,7 +8427,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8503,7 +8507,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8620,12 +8624,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8677,7 +8681,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10118,7 +10122,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10498,7 +10502,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10577,7 +10581,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10603,7 +10607,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10815,9 +10819,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10862,7 +10866,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10908,7 +10912,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10919,7 +10923,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -10990,7 +10994,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11010,7 +11014,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19392,7 +19396,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "כלים"
 
@@ -22327,8 +22331,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22541,9 +22544,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24528,7 +24531,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25260,437 +25263,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27456,7 +27028,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27466,7 +27038,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42761,9 +42333,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42813,9 +42385,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42869,46 +42441,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42916,7 +42486,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42925,7 +42495,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42933,7 +42503,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42943,7 +42513,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -42954,19 +42524,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -42974,13 +42544,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -42988,7 +42558,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -42997,7 +42567,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43011,7 +42581,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43020,7 +42590,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43028,10 +42598,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -43996,6 +43566,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46911,6 +46486,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51455,11 +51456,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51653,73 +51654,70 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51727,131 +51725,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51859,55 +51853,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51918,22 +51912,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51942,7 +51936,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -51950,11 +51944,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -51963,42 +51957,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52008,7 +52009,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52017,7 +52018,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52025,58 +52026,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54167,7 +54365,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54175,18 +54373,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54194,23 +54392,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54218,35 +54416,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54255,103 +54453,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54359,20 +54557,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54411,11 +54609,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54425,24 +54635,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54451,7 +54661,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54459,18 +54669,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54480,7 +54690,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54489,37 +54699,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54527,63 +54737,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54591,13 +54801,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54605,7 +54815,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54613,25 +54823,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54639,30 +54849,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54670,7 +54880,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54679,25 +54889,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54708,46 +54918,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54756,68 +54966,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54825,7 +55035,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54834,11 +55044,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54846,114 +55056,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55020,37 +55230,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55058,61 +55268,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55132,18 +55342,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55151,11 +55361,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55163,37 +55373,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55254,27 +55464,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55282,24 +55492,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55307,29 +55504,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55337,35 +55534,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55373,40 +55570,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55414,131 +55611,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55558,29 +55755,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55591,17 +55788,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "הרצה"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55711,6 +55908,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55795,61 +55996,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55858,13 +56059,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55873,11 +56074,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55885,14 +56086,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55900,14 +56101,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55916,14 +56117,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55933,7 +56134,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55942,7 +56143,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -55951,7 +56152,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -55982,7 +56183,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -55992,7 +56193,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56000,14 +56201,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56015,21 +56216,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56038,7 +56239,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56048,7 +56249,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/hi.po b/weblate/hi.po
index 577a7b2732..40bb839b3f 100644
--- a/weblate/hi.po
+++ b/weblate/hi.po
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-10-07 19:28+0000\n"
 "Last-Translator: Vikram1323 <vikram1323@gmail.com>\n"
 "Language-Team: Hindi <https://hosted.weblate.org/projects/godot-engine/godot-"
@@ -70,13 +70,14 @@ msgstr ""
 "रहे हैं वह नहीं मिल पा रहे हैं, तो हमें  बता कर दस्तावेज को बेहतर बनाने में मदद करें!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "' GitHub भंडार < https://github.com/godotengine/godot-docs/issues > ' _ पर एक "
 "मुद्दा (issue) या पुल अनुरोध (pull request) सबमिट करें। प्रलेखन के अनुवाद मे हमारी मदद "
@@ -148,7 +149,6 @@ msgstr "के बारे में"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -167,6 +167,7 @@ msgstr "के बारे में"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -314,9 +315,9 @@ msgstr ""
 
 #: ../../docs/about/introduction.rst:85
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1257,7 +1258,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1724,7 +1725,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1799,13 +1800,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2049,8 +2050,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2074,7 +2075,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2148,7 +2149,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2162,7 +2163,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2502,6 +2503,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "संकेत"
@@ -2972,7 +2974,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3098,7 +3100,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3307,7 +3309,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3405,7 +3407,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3433,7 +3435,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -3931,7 +3933,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -3987,8 +3989,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4064,7 +4066,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4161,7 +4163,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4247,14 +4249,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4363,7 +4365,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4409,7 +4411,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4449,7 +4451,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4490,9 +4492,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4580,7 +4582,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4697,7 +4699,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4745,7 +4747,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4887,7 +4889,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -4995,7 +4997,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5019,7 +5021,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5346,9 +5348,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5378,8 +5381,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5419,8 +5423,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6322,7 +6326,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6391,9 +6395,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6410,12 +6414,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6438,8 +6442,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6615,10 +6620,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6697,16 +6702,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6717,7 +6722,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6759,7 +6764,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6786,7 +6791,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -6935,7 +6940,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -6950,7 +6955,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7028,7 +7033,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7055,7 +7060,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7192,9 +7197,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7263,16 +7268,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7289,14 +7294,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7327,16 +7332,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7398,7 +7403,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7428,7 +7433,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7574,7 +7579,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7604,7 +7609,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7636,7 +7641,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8071,9 +8076,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8382,7 +8387,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8462,7 +8467,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8579,12 +8584,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8636,7 +8641,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10071,7 +10076,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10451,7 +10456,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10530,7 +10535,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10556,7 +10561,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10767,9 +10772,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10814,7 +10819,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10860,7 +10865,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10871,7 +10876,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -10942,7 +10947,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -10962,7 +10967,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19337,7 +19342,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -22271,8 +22276,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22485,9 +22489,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24472,7 +24476,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25203,437 +25207,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27399,7 +26972,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27409,7 +26982,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42703,9 +42276,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42755,9 +42328,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42811,46 +42384,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42858,7 +42429,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42867,7 +42438,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42875,7 +42446,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42885,7 +42456,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -42896,19 +42467,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -42916,13 +42487,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -42930,7 +42501,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -42939,7 +42510,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -42953,7 +42524,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -42962,7 +42533,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -42970,10 +42541,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -43938,6 +43509,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46853,6 +46429,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51397,11 +51399,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51595,73 +51597,70 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51669,131 +51668,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51801,55 +51796,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51860,22 +51855,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51884,7 +51879,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -51892,11 +51887,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -51905,42 +51900,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -51950,7 +51952,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -51959,7 +51961,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -51967,58 +51969,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54108,7 +54307,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54116,18 +54315,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54135,23 +54334,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54159,35 +54358,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54196,103 +54395,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54300,20 +54499,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54352,11 +54551,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54366,24 +54577,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54392,7 +54603,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54400,18 +54611,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54421,7 +54632,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54430,37 +54641,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54468,63 +54679,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54532,13 +54743,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54546,7 +54757,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54554,25 +54765,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54580,30 +54791,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54611,7 +54822,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54620,25 +54831,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54649,46 +54860,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54697,68 +54908,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54766,7 +54977,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54775,11 +54986,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54787,114 +54998,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -54961,37 +55172,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -54999,61 +55210,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55073,18 +55284,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55092,11 +55303,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55104,37 +55315,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55195,27 +55406,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55223,24 +55434,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55248,29 +55446,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55278,35 +55476,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55314,40 +55512,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55355,131 +55553,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55499,29 +55697,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55532,17 +55730,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55652,6 +55850,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55736,61 +55938,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55799,13 +56001,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55814,11 +56016,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55826,14 +56028,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55841,14 +56043,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55857,14 +56059,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55874,7 +56076,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55883,7 +56085,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -55892,7 +56094,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -55923,7 +56125,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -55933,7 +56135,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -55941,14 +56143,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -55956,21 +56158,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -55979,7 +56181,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -55989,7 +56191,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/hu.po b/weblate/hu.po
index 361589b089..0154637c7d 100644
--- a/weblate/hu.po
+++ b/weblate/hu.po
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-06-17 16:39+0000\n"
 "Last-Translator: Árpád Horváth <horvatha4@googlemail.com>\n"
 "Language-Team: Hungarian <https://hosted.weblate.org/projects/godot-engine/"
@@ -73,13 +73,14 @@ msgstr ""
 "azáltal, hogy tudatja velünk!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Küldje el a problémát, vagy kérjen behúzást a `GitHub repository  <https://"
 "github.com/godotengine/godot-docs/issues> `_, segítsen nekünk `translate the "
@@ -152,7 +153,6 @@ msgstr "Névjegy"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -171,6 +171,7 @@ msgstr "Névjegy"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -369,10 +370,11 @@ msgstr ""
 "fordításához, C++ modulok vagy szerkesztő-bővítmények fejlesztéséhez."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1339,7 +1341,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1806,7 +1808,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1881,13 +1883,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2131,8 +2133,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2156,7 +2158,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2230,7 +2232,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2244,7 +2246,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2584,6 +2586,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Jelzések"
@@ -3055,7 +3058,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3181,7 +3184,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3391,7 +3394,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3489,7 +3492,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3517,7 +3520,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -4015,7 +4018,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4072,8 +4075,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4149,7 +4152,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4246,7 +4249,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4332,14 +4335,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4448,7 +4451,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4494,7 +4497,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4534,7 +4537,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4575,9 +4578,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4665,7 +4668,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4782,7 +4785,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4830,7 +4833,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4972,7 +4975,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5080,7 +5083,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5104,7 +5107,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5431,9 +5434,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5463,8 +5467,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5504,8 +5509,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6407,7 +6412,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6476,9 +6481,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6495,12 +6500,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6523,8 +6528,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6700,10 +6706,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6782,16 +6788,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6802,7 +6808,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6844,7 +6850,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6871,7 +6877,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -7020,7 +7026,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7035,7 +7041,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7113,7 +7119,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7140,7 +7146,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7277,9 +7283,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7348,16 +7354,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7374,14 +7380,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7412,16 +7418,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7483,7 +7489,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7513,7 +7519,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7659,7 +7665,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7689,7 +7695,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7721,7 +7727,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8156,9 +8162,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8468,7 +8474,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8548,7 +8554,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8665,12 +8671,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8722,7 +8728,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10159,7 +10165,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10539,7 +10545,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10618,7 +10624,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10644,7 +10650,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10856,9 +10862,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10903,7 +10909,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10949,7 +10955,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10960,7 +10966,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11031,7 +11037,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11051,7 +11057,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19434,7 +19440,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "Eszközök"
 
@@ -22369,8 +22375,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22583,9 +22588,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24570,7 +24575,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25301,437 +25306,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27497,7 +27071,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27507,7 +27081,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42803,9 +42377,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42855,9 +42429,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42911,46 +42485,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42958,7 +42530,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42967,7 +42539,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42975,7 +42547,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42985,7 +42557,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -42996,19 +42568,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -43016,13 +42588,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43030,7 +42602,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43039,7 +42611,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43053,7 +42625,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43062,7 +42634,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43070,10 +42642,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44038,6 +43610,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46953,6 +46530,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51498,11 +51501,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51696,45 +51699,41 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -51743,29 +51742,30 @@ msgstr ""
 "Ezen dokumentáció mellett megtekinthető még különböző `Godot demo projects "
 "<https://github.com/godotengine/godot-demo-projects>`_."
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51773,131 +51773,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51905,55 +51901,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51964,22 +51960,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51988,7 +51984,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -51996,11 +51992,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -52009,42 +52005,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52054,7 +52057,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52063,7 +52066,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52071,58 +52074,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54212,7 +54412,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54220,18 +54420,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54239,23 +54439,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54263,35 +54463,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54300,103 +54500,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54404,20 +54604,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54456,11 +54656,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54470,24 +54682,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54496,7 +54708,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54504,18 +54716,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54525,7 +54737,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54534,37 +54746,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54572,63 +54784,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54636,13 +54848,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54650,7 +54862,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54658,25 +54870,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54684,30 +54896,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54715,7 +54927,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54724,25 +54936,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54753,46 +54965,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54801,68 +55013,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54870,7 +55082,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54879,11 +55091,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54891,114 +55103,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55065,37 +55277,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55103,61 +55315,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55177,18 +55389,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55196,11 +55408,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55208,37 +55420,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55299,27 +55511,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55327,24 +55539,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55352,29 +55551,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55382,35 +55581,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55418,40 +55617,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55459,131 +55658,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55603,29 +55802,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55636,17 +55835,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "Futtatás"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55756,6 +55955,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55840,61 +56043,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55903,13 +56106,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55918,11 +56121,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55930,14 +56133,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55945,14 +56148,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55961,14 +56164,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55978,7 +56181,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55987,7 +56190,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -55996,7 +56199,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56027,7 +56230,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56037,7 +56240,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56045,14 +56248,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56060,21 +56263,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56083,7 +56286,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56093,7 +56296,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/id.po b/weblate/id.po
index 4bb08d03fd..4a49c2b591 100644
--- a/weblate/id.po
+++ b/weblate/id.po
@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-06-30 03:38+0000\n"
 "Last-Translator: Khairul Hidayat <khairulcyber4rt@gmail.com>\n"
 "Language-Team: Indonesian <https://hosted.weblate.org/projects/godot-engine/"
@@ -78,13 +78,14 @@ msgstr ""
 "dokumentasi yang lebih baik dengan memberi tahu kami!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Sampaikan isu atau permintaan pull request di `repositori GitHub <https://"
 "github.com/godotengine/godot-docs/issues>`_, bantu kami `menerjemahkan "
@@ -157,7 +158,6 @@ msgstr "Tentang"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -176,6 +176,7 @@ msgstr "Tentang"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -376,10 +377,11 @@ msgstr ""
 "berbasis C++."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1341,7 +1343,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1808,7 +1810,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1883,13 +1885,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2133,8 +2135,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2158,7 +2160,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2232,7 +2234,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2246,7 +2248,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2586,6 +2588,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr ""
@@ -3056,7 +3059,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3182,7 +3185,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3391,7 +3394,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3489,7 +3492,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3517,7 +3520,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -4015,7 +4018,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4071,8 +4074,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4148,7 +4151,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4245,7 +4248,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4331,14 +4334,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4447,7 +4450,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4493,7 +4496,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4533,7 +4536,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4574,9 +4577,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4664,7 +4667,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4781,7 +4784,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4829,7 +4832,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4971,7 +4974,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5079,7 +5082,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5103,7 +5106,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5430,9 +5433,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5462,8 +5466,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5503,8 +5508,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6406,7 +6411,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6475,9 +6480,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6494,12 +6499,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6522,8 +6527,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6699,10 +6705,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6781,16 +6787,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6801,7 +6807,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6843,7 +6849,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6870,7 +6876,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -7019,7 +7025,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7034,7 +7040,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7112,7 +7118,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7139,7 +7145,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7276,9 +7282,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7347,16 +7353,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7373,14 +7379,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7411,16 +7417,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7482,7 +7488,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7512,7 +7518,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7658,7 +7664,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7688,7 +7694,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7720,7 +7726,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8155,9 +8161,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8467,7 +8473,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8547,7 +8553,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8664,12 +8670,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8721,7 +8727,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10157,7 +10163,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10537,7 +10543,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10616,7 +10622,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10642,7 +10648,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10853,9 +10859,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10900,7 +10906,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10946,7 +10952,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10957,7 +10963,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11028,7 +11034,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11048,7 +11054,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19421,7 +19427,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -22355,8 +22361,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22569,9 +22574,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24556,7 +24561,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25287,437 +25292,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27483,7 +27057,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27493,7 +27067,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42786,9 +42360,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42838,9 +42412,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42894,46 +42468,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42941,7 +42513,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42950,7 +42522,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42958,7 +42530,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42968,7 +42540,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -42979,19 +42551,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -42999,13 +42571,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43013,7 +42585,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43022,7 +42594,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43036,7 +42608,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43045,7 +42617,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43053,10 +42625,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44021,6 +43593,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46936,6 +46513,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51480,11 +51483,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51678,45 +51681,41 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -51726,29 +51725,30 @@ msgstr ""
 "berbagai `proyek demo Godot <https://github.com/godotengine/godot-demo-"
 "projects>`_."
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51756,131 +51756,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51888,55 +51884,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51947,22 +51943,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51971,7 +51967,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -51979,11 +51975,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -51992,42 +51988,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52037,7 +52040,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52046,7 +52049,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52054,58 +52057,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54195,7 +54395,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54203,18 +54403,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54222,23 +54422,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54246,35 +54446,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54283,103 +54483,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54387,20 +54587,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54439,11 +54639,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54453,24 +54665,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54479,7 +54691,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54487,18 +54699,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54508,7 +54720,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54517,37 +54729,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54555,63 +54767,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54619,13 +54831,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54633,7 +54845,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54641,25 +54853,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54667,30 +54879,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54698,7 +54910,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54707,25 +54919,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54736,46 +54948,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54784,68 +54996,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54853,7 +55065,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54862,11 +55074,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54874,114 +55086,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55048,37 +55260,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55086,61 +55298,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55160,18 +55372,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55179,11 +55391,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55191,37 +55403,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55282,27 +55494,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55310,24 +55522,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55335,29 +55534,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55365,35 +55564,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55401,40 +55600,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55442,131 +55641,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55586,29 +55785,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55619,17 +55818,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55739,6 +55938,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55823,61 +56026,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55886,13 +56089,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55901,11 +56104,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55913,14 +56116,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55928,14 +56131,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55944,14 +56147,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55961,7 +56164,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55970,7 +56173,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -55979,7 +56182,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56010,7 +56213,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56020,7 +56223,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56028,14 +56231,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56043,21 +56246,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56066,7 +56269,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56076,7 +56279,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/it.po b/weblate/it.po
index 20d2f5f62c..e9d59b94d2 100644
--- a/weblate/it.po
+++ b/weblate/it.po
@@ -25,7 +25,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-11-18 17:07+0000\n"
 "Last-Translator: Davide Wayan Mores <moresdavidewayan@gmail.com>\n"
 "Language-Team: Italian <https://hosted.weblate.org/projects/godot-engine/"
@@ -92,13 +92,14 @@ msgstr ""
 "facendocelo sapere!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Invia un problema o una richiesta sul `repository di GitHub <https://github."
 "com/godotengine/godot-docs/issues>`_, aiutaci a `tradurre la documentazione "
@@ -173,7 +174,6 @@ msgstr "Riguardo a"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -192,6 +192,7 @@ msgstr "Riguardo a"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -392,10 +393,11 @@ msgstr ""
 "l'editor."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1674,7 +1676,8 @@ msgid "It can be extended (to have more functions)."
 msgstr "Puó essere esteso (per aggiungere funzionalitá)."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+#, fuzzy
+msgid "It can be added to another node as a child."
 msgstr "Puó essere aggiunto ad altri nodi come figlio."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -2309,13 +2312,14 @@ msgstr ""
 "direttamente nell'editor) per i rapporti di proprietà."
 
 #: ../../docs/getting_started/step_by_step/instancing_continued.rst:43
+#, fuzzy
 msgid ""
 "A lot of time spent in programming games (or software in general) is on "
 "designing an architecture and fitting game components to that architecture. "
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 "Molto tempo speso nella programmazione dei giochi (o del software in "
@@ -2400,13 +2404,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2650,8 +2654,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2675,7 +2679,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2749,7 +2753,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2763,7 +2767,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -3103,6 +3107,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Segnali"
@@ -3595,7 +3600,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3721,7 +3726,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3931,7 +3936,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -4029,7 +4034,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -4057,7 +4062,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -4556,7 +4561,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4612,8 +4617,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4689,7 +4694,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4786,7 +4791,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4872,14 +4877,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4988,7 +4993,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -5034,7 +5039,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -5074,7 +5079,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -5115,9 +5120,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -5205,7 +5210,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -5322,7 +5327,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -5370,7 +5375,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -5512,7 +5517,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5620,7 +5625,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5644,7 +5649,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5971,9 +5976,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -6003,8 +6009,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -6044,8 +6051,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6947,7 +6954,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -7016,9 +7023,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -7035,12 +7042,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -7063,8 +7070,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -7240,10 +7248,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -7322,16 +7330,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -7342,7 +7350,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -7384,7 +7392,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -7411,7 +7419,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -7560,7 +7568,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7575,7 +7583,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7653,7 +7661,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7680,7 +7688,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7817,9 +7825,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7888,16 +7896,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7914,14 +7922,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7952,16 +7960,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -8023,7 +8031,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -8054,7 +8062,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -8200,7 +8208,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -8230,7 +8238,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -8262,7 +8270,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8697,9 +8705,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -9009,7 +9017,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -9089,7 +9097,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -9206,12 +9214,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -9263,7 +9271,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10702,7 +10710,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -11082,7 +11090,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -11161,7 +11169,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -11187,7 +11195,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -11399,9 +11407,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -11446,7 +11454,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -11492,7 +11500,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -11503,7 +11511,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11574,7 +11582,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11594,7 +11602,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19978,7 +19986,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "Strumenti"
 
@@ -22912,8 +22920,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -23126,9 +23133,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -25115,7 +25122,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25847,437 +25854,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -28043,7 +27619,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -28053,7 +27629,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -43347,9 +42923,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -43399,9 +42975,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -43455,46 +43031,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -43502,7 +43076,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -43511,7 +43085,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -43519,7 +43093,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -43529,7 +43103,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -43540,19 +43114,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -43560,13 +43134,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43574,7 +43148,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43583,7 +43157,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43597,7 +43171,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43606,7 +43180,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43614,10 +43188,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44582,6 +44156,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -47497,6 +47076,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -52041,11 +52046,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -52239,45 +52244,41 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -52287,29 +52288,30 @@ msgstr ""
 "vari `Progetti dimostativi (Godot demo projects <https://github.com/"
 "godotengine/godot-demo-projects>`_."
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -52317,131 +52319,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -52449,55 +52447,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -52508,22 +52506,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -52532,7 +52530,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -52540,11 +52538,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -52553,42 +52551,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52598,7 +52603,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52607,7 +52612,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52615,58 +52620,256 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+#, fuzzy
+msgid "Adding properties"
+msgstr "Ha delle proprietá modificabili."
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54757,7 +54960,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54765,18 +54968,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54784,23 +54987,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54808,35 +55011,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54845,103 +55048,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54949,20 +55152,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -55001,11 +55204,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -55015,24 +55230,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -55041,7 +55256,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -55049,18 +55264,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -55070,7 +55285,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -55079,37 +55294,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -55117,63 +55332,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -55181,13 +55396,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -55195,7 +55410,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -55203,25 +55418,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -55229,30 +55444,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -55260,7 +55475,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -55269,25 +55484,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -55298,46 +55513,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -55346,68 +55561,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -55415,7 +55630,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -55424,11 +55639,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -55436,114 +55651,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55610,37 +55825,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55648,61 +55863,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55722,18 +55937,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55741,11 +55956,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55753,37 +55968,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55844,27 +56059,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55872,24 +56087,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55897,29 +56099,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55927,35 +56129,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55963,40 +56165,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -56004,131 +56206,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -56148,29 +56350,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -56181,17 +56383,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -56301,6 +56503,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -56385,61 +56591,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -56448,13 +56654,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -56463,11 +56669,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -56475,14 +56681,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -56490,14 +56696,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -56506,14 +56712,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -56523,7 +56729,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -56532,7 +56738,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -56541,7 +56747,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56572,7 +56778,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56582,7 +56788,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56590,14 +56796,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56605,21 +56811,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56628,7 +56834,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56638,7 +56844,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/ja.po b/weblate/ja.po
index 871671de98..51aa3ed94d 100644
--- a/weblate/ja.po
+++ b/weblate/ja.po
@@ -13,7 +13,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-10-17 05:31+0000\n"
 "Last-Translator: Hidetsugu Takahashi <manzyun@gmail.com>\n"
 "Language-Team: Japanese <https://hosted.weblate.org/projects/godot-engine/"
@@ -75,13 +75,14 @@ msgstr ""
 "えてください！"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "`GitHub リポジトリ <https://github.com/godotengine/godot-docs/issues>`_にイ"
 "シューを投稿またはプルリクエストをするか、あなたが使用する言語に`ドキュメント"
@@ -154,7 +155,6 @@ msgstr "概要"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -173,6 +173,7 @@ msgstr "概要"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -363,10 +364,11 @@ msgstr ""
 "貢献者を対象としています。"
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1333,7 +1335,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1800,7 +1802,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1875,13 +1877,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2125,8 +2127,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2150,7 +2152,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2224,7 +2226,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2238,7 +2240,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2578,6 +2580,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "信号"
@@ -3049,7 +3052,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3176,7 +3179,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3386,7 +3389,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3484,7 +3487,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3512,7 +3515,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -4011,7 +4014,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4068,8 +4071,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4145,7 +4148,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4242,7 +4245,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4328,14 +4331,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4445,7 +4448,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4491,7 +4494,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4531,7 +4534,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4572,9 +4575,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4662,7 +4665,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4779,7 +4782,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4827,7 +4830,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4969,7 +4972,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5077,7 +5080,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5101,7 +5104,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5428,9 +5431,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5460,8 +5464,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5501,8 +5506,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6404,7 +6409,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6473,9 +6478,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6492,12 +6497,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6520,8 +6525,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6697,10 +6703,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6779,16 +6785,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6799,7 +6805,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6841,7 +6847,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6868,7 +6874,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -7017,7 +7023,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7032,7 +7038,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7110,7 +7116,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7137,7 +7143,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7274,9 +7280,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7345,16 +7351,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7371,14 +7377,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7409,16 +7415,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7480,7 +7486,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7510,7 +7516,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7656,7 +7662,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7686,7 +7692,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7718,7 +7724,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8153,9 +8159,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8465,7 +8471,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8545,7 +8551,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8662,12 +8668,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8719,7 +8725,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10157,7 +10163,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10537,7 +10543,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10616,7 +10622,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10642,7 +10648,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10853,9 +10859,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10900,7 +10906,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10946,7 +10952,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10957,7 +10963,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11028,7 +11034,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11048,7 +11054,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19429,7 +19435,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "ツール"
 
@@ -22363,8 +22369,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22577,9 +22582,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24564,7 +24569,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25295,437 +25300,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27491,7 +27065,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27501,7 +27075,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42798,9 +42372,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42850,9 +42424,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42906,46 +42480,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42953,7 +42525,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42962,7 +42534,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42970,7 +42542,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42980,7 +42552,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -42991,19 +42563,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -43011,13 +42583,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43025,7 +42597,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43034,7 +42606,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43048,7 +42620,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43057,7 +42629,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43065,10 +42637,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44033,6 +43605,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46949,6 +46526,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51494,11 +51497,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51692,73 +51695,70 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51766,131 +51766,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51898,55 +51894,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51957,22 +51953,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51981,7 +51977,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -51989,11 +51985,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -52002,42 +51998,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52047,7 +52050,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52056,7 +52059,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52064,58 +52067,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54205,7 +54405,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54213,18 +54413,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54232,23 +54432,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54256,35 +54456,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54293,103 +54493,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54397,20 +54597,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54449,11 +54649,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54463,24 +54675,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54489,7 +54701,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54497,18 +54709,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54518,7 +54730,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54527,37 +54739,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54565,63 +54777,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54629,13 +54841,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54643,7 +54855,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54651,25 +54863,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54677,30 +54889,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54708,7 +54920,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54717,25 +54929,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54746,46 +54958,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54794,68 +55006,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54863,7 +55075,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54872,11 +55084,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54884,114 +55096,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55058,37 +55270,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55096,61 +55308,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55170,18 +55382,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55189,11 +55401,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55201,37 +55413,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55292,27 +55504,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55320,24 +55532,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55345,29 +55544,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55375,35 +55574,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55411,40 +55610,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55452,131 +55651,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55596,29 +55795,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55629,17 +55828,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "実行"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55749,6 +55948,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55833,61 +56036,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55896,13 +56099,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55911,11 +56114,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55923,14 +56126,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55938,14 +56141,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55954,14 +56157,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55971,7 +56174,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55980,7 +56183,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -55989,7 +56192,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56020,7 +56223,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56030,7 +56233,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56038,14 +56241,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56053,21 +56256,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56076,7 +56279,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56086,7 +56289,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/jbo.po b/weblate/jbo.po
index 027f7fa353..9a453e9254 100644
--- a/weblate/jbo.po
+++ b/weblate/jbo.po
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-11-20 10:45+0000\n"
 "Last-Translator: Kyle Serdutz <KyleSerdutz@mail.com>\n"
 "Language-Team: Lojban <https://hosted.weblate.org/projects/godot-engine/"
@@ -69,9 +69,9 @@ msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 
 #: ../../docs/index.rst:43
@@ -137,7 +137,6 @@ msgstr ""
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -156,6 +155,7 @@ msgstr ""
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -296,9 +296,9 @@ msgstr ""
 
 #: ../../docs/about/introduction.rst:85
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1239,7 +1239,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1706,7 +1706,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1781,13 +1781,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2031,8 +2031,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2056,7 +2056,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2130,7 +2130,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2144,7 +2144,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2484,6 +2484,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr ""
@@ -2954,7 +2955,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3080,7 +3081,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3289,7 +3290,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3387,7 +3388,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3415,7 +3416,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -3913,7 +3914,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -3969,8 +3970,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4046,7 +4047,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4143,7 +4144,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4229,14 +4230,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4345,7 +4346,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4391,7 +4392,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4431,7 +4432,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4472,9 +4473,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4562,7 +4563,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4679,7 +4680,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4727,7 +4728,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4869,7 +4870,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -4977,7 +4978,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5001,7 +5002,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5328,9 +5329,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5360,8 +5362,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5401,8 +5404,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6304,7 +6307,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6373,9 +6376,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6392,12 +6395,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6420,8 +6423,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6597,10 +6601,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6679,16 +6683,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6699,7 +6703,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6741,7 +6745,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6768,7 +6772,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -6917,7 +6921,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -6932,7 +6936,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7010,7 +7014,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7037,7 +7041,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7174,9 +7178,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7245,16 +7249,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7271,14 +7275,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7309,16 +7313,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7380,7 +7384,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7410,7 +7414,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7556,7 +7560,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7586,7 +7590,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7618,7 +7622,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8053,9 +8057,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8364,7 +8368,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8444,7 +8448,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8561,12 +8565,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8618,7 +8622,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10053,7 +10057,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10433,7 +10437,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10512,7 +10516,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10538,7 +10542,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10749,9 +10753,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10796,7 +10800,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10842,7 +10846,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10853,7 +10857,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -10924,7 +10928,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -10944,7 +10948,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19317,7 +19321,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -22251,8 +22255,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22465,9 +22468,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24451,7 +24454,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25182,437 +25185,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27378,7 +26950,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27388,7 +26960,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42681,9 +42253,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42733,9 +42305,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42789,46 +42361,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42836,7 +42406,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42845,7 +42415,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42853,7 +42423,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42863,7 +42433,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -42874,19 +42444,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -42894,13 +42464,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -42908,7 +42478,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -42917,7 +42487,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -42931,7 +42501,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -42940,7 +42510,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -42948,10 +42518,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -43916,6 +43486,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46831,6 +46406,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51375,11 +51376,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51573,73 +51574,70 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51647,131 +51645,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51779,55 +51773,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51838,22 +51832,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51862,7 +51856,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -51870,11 +51864,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -51883,42 +51877,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -51928,7 +51929,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -51937,7 +51938,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -51945,58 +51946,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54086,7 +54284,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54094,18 +54292,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54113,23 +54311,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54137,35 +54335,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54174,103 +54372,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54278,20 +54476,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54330,11 +54528,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54344,24 +54554,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54370,7 +54580,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54378,18 +54588,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54399,7 +54609,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54408,37 +54618,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54446,63 +54656,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54510,13 +54720,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54524,7 +54734,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54532,25 +54742,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54558,30 +54768,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54589,7 +54799,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54598,25 +54808,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54627,46 +54837,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54675,68 +54885,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54744,7 +54954,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54753,11 +54963,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54765,114 +54975,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -54939,37 +55149,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -54977,61 +55187,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55051,18 +55261,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55070,11 +55280,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55082,37 +55292,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55173,27 +55383,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55201,24 +55411,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55226,29 +55423,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55256,35 +55453,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55292,40 +55489,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55333,131 +55530,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55477,29 +55674,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55510,17 +55707,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55630,6 +55827,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55714,61 +55915,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55777,13 +55978,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55792,11 +55993,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55804,14 +56005,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55819,14 +56020,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55835,14 +56036,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55852,7 +56053,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55861,7 +56062,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -55870,7 +56071,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -55901,7 +56102,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -55911,7 +56112,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -55919,14 +56120,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -55934,21 +56135,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -55957,7 +56158,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -55967,7 +56168,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/ko.po b/weblate/ko.po
index 0f45f2264f..6dcdaca110 100644
--- a/weblate/ko.po
+++ b/weblate/ko.po
@@ -26,7 +26,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-12-04 00:30+0000\n"
 "Last-Translator: 송태섭 <xotjq237@gmail.com>\n"
 "Language-Team: Korean <https://hosted.weblate.org/projects/godot-engine/"
@@ -88,13 +88,14 @@ msgstr ""
 "주세요!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "`GitHub 저장소 <https://github.com/godotengine/godot-docs/issues>`_\\ 에서 이"
 "슈를 제출하거나, `문서 현지화 <https://hosted.weblate.org/engage/godot-"
@@ -166,7 +167,6 @@ msgstr "정보"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -185,6 +185,7 @@ msgstr "정보"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -371,10 +372,11 @@ msgstr ""
 "진 컴파일, C++ 모듈 혹은 에디터 플러그인 개발에 대한 정보를 담고 있습니다."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1561,7 +1563,8 @@ msgid "It can be extended (to have more functions)."
 msgstr "(더 많은 기능을 위해) 확장될 수 있습니다."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+#, fuzzy
+msgid "It can be added to another node as a child."
 msgstr "다른 노드에 자식으로 추가될 수 있습니다."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -2154,13 +2157,14 @@ msgstr ""
 "스턴스를 사용할 것입니다, 소유 관계를 위해서 말입니다."
 
 #: ../../docs/getting_started/step_by_step/instancing_continued.rst:43
+#, fuzzy
 msgid ""
 "A lot of time spent in programming games (or software in general) is on "
 "designing an architecture and fitting game components to that architecture. "
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 "게임을 프로그래밍할 때, 혹은 일반적으로 소프트웨어를 짤 때 가장 오래 걸리는 "
@@ -2260,16 +2264,18 @@ msgstr ""
 "를 추가하는 기능도 있습니다!"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
+#, fuzzy
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 "이것은 대단합니다, 기존의 경우에는 유연성을 제공해 주었지만, 다른 언어를 지원"
 "하기 어렵게 만들기도 했습니다."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
+#, fuzzy
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2574,9 +2580,10 @@ msgstr ""
 "명 및 기타 관련 옵션을 설정할 수 있습니다."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
+#, fuzzy
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 "GDScript에서 파일 자체는 클래스를 나타내므로 클래스명 부분은 편집할 수 없습니"
 "다."
@@ -2606,9 +2613,10 @@ msgstr ""
 "서도 볼 수 있습니다:"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
+#, fuzzy
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 "스크립트를 편집하려면 위 이미지에 강조 표시된 두 버튼 중 하나를 선택합니다. "
@@ -2703,11 +2711,12 @@ msgstr ""
 "는 메서드를 실행할 (NodePath로 정의된) 하나의 노드와 그 메서드의 이름입니다."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:205
+#, fuzzy
 msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 "왼쪽 위 구역은 씬에 있는 노드들을 보여주며 방출하는 노드 이름은 빨갛게 표시됩"
 "니다. \"Panel\" 노드를 선택해봅시다. 노드를 선택하면, 밑에 NodePath가 자동으"
@@ -2727,9 +2736,10 @@ msgstr ""
 "에 함수를 생성할 겁니다."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
+#, fuzzy
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 "그리고 이것으로 시각 인터페이스를 사용하는 법에 관한 강좌를 마칩니다. 하지"
@@ -3171,6 +3181,7 @@ msgstr "오직 GDScript만 각 이름이 있는 스크립트에 전역 변수를
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "시그널(Signal)"
@@ -3798,10 +3809,11 @@ msgstr ""
 "기를 알아보기 좋은 순간입니다:"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:198
+#, fuzzy
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 "이제 우리는 ``_process()`` 함수를 사용해서 플레이어가 무엇을 할 지 정의할 수 "
 "있습니다. ``_process()`` 는 매 프레임마다 호출되므로, 게임에서 자주 업데이트 "
@@ -3972,10 +3984,11 @@ msgstr ""
 "할당을 이 코드와 비교해서 생각해보세요:"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:372
+#, fuzzy
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 "씬을 다시 실행하고 애니메이션이 각 방향에 맞게 되는지 확인하세요. 잘 작동된다"
 "고 확신된다면, 플레이어가 게임이 시작할 때 안 보이도록 이 문장을 "
@@ -4244,8 +4257,9 @@ msgid "See :ref:`doc_instancing` to learn more about instancing."
 msgstr "인스턴스에 대해 더 알고 싶다면 :ref:`doc_instancing` 로 가세요."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
+#, fuzzy
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 "``Main`` 의 자식으로 다음의 노드들을 추가하고, 보이는 대로 이름을 지으세요 "
@@ -4370,8 +4384,9 @@ msgid "Main script"
 msgstr "메인 스크립트"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
+#, fuzzy
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 "``Main`` 에 스크립트를 추가합니다. 스크립트의 위에 ``export (PackedScene)`` "
@@ -4410,8 +4425,9 @@ msgstr ""
 "하게 만들 것입니다. ``ScoreTimer`` 는 점수가 1씩 증가하게 합니다."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
+#, fuzzy
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -5030,7 +5046,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr "템플릿 내보내기"
@@ -5100,9 +5116,10 @@ msgstr ""
 "다, 마치 안드로이드의 `.apk` 나 윈도우의 `.exe` 처럼 말이죠."
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
+#, fuzzy
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 "\"리소스\"와 \"기능\" 탭에서 당신은 각 플랫폼에 게임이 어떻게 내보내게 될지"
 "를 설정합니다. 지금은 이 설정으로 두어도 됩니다."
@@ -5198,8 +5215,9 @@ msgstr ""
 "도록 만드는 `adb` 명령 행 도구를 실행시킵니다."
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
+#, fuzzy
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 "다음으로, 시스템의 명령 행에 다음의 명령을 실행시켜 디버그 키 저장소를 만드세"
@@ -5320,9 +5338,10 @@ msgid ""
 msgstr "내보내기가 끝나면, 다음의 파일이 들어있는 폴더를 찾으실 수 있습니다:"
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
+#, fuzzy
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -5437,9 +5456,10 @@ msgid "On top of that, you can **inherit** from any scene."
 msgstr "무엇보다도, 당신이 어떤 씬에서든지 **상속하는 것** 이 가능합니다."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
+#, fuzzy
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
@@ -5449,8 +5469,9 @@ msgstr ""
 "한 코드처럼 작동합니다."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
+#, fuzzy
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -5600,9 +5621,10 @@ msgstr ""
 "니다."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
+#, fuzzy
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -5665,8 +5687,9 @@ msgstr ""
 "니다."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
+#, fuzzy
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 "이로인해 에디터 자체에 권한을 부여하여 안정적이고 유연한 UI 시스템이 탄생하"
@@ -5714,11 +5737,12 @@ msgid "Design interfaces with the Control nodes"
 msgstr "컨트롤(Control) 노드로 인터페이스를 설계하기"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:6
+#, fuzzy
 msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -5769,11 +5793,12 @@ msgstr ""
 "your first game UI in Godot <doc_ui_game_user_interface>` 를 읽어주세요."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
+#, fuzzy
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 "인터페이스를 설계할 때 오직 컨트롤 노드만 사용합니다. 그들은 서로 작동하게 하"
@@ -5873,9 +5898,10 @@ msgid "TextureRect"
 msgstr "TextureRect"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
+#, fuzzy
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 "**TextureRect** 은 UI 내에 텍스쳐나 이미지를 보여줍니다. 이것은 Sprite 노드"
@@ -6025,12 +6051,13 @@ msgid "TextureProgress bar, two thirds filled"
 msgstr "3분의 2가 채워진 TextureProgress 막대"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:143
+#, fuzzy
 msgid ""
 "**Label** prints text to the screen. You'll find all its properties in the "
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 "**Label** 은 문자를 화면에 보여줍니다. 당신은 이것의 모든 속성을 인스펙터의 "
 "Label 섹션에서 찾으실 수 있습니다. ``Text`` 속성에서 문자를 쓰고, 텍스트 상자"
@@ -6089,10 +6116,11 @@ msgstr ""
 "및 배치하고 크기 조절하도록 돕습니다."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:174
+#, fuzzy
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -6278,11 +6306,12 @@ msgid "Arrange control nodes automatically with containers"
 msgstr "컨테이너로 컨트롤 노드를 자동으로 배열하기"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:275
+#, fuzzy
 msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 "컨테이너는 자동으로 모든 자식 컨트롤 노드와 자식 컨테이너들을 열이나 행이나 "
 "그 밖의 형태로 배열합니다. 컨테이너를 사용해서 이것의 경계 사각형 내에서 인터"
@@ -6423,9 +6452,10 @@ msgid "A GridContainer with 2 columns. It sizes each column automatically."
 msgstr "2열로 된 GridContainer. 각 행은 자동으로 크기가 조절됩니다."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
+#, fuzzy
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 "Godot의 UI 시스템은 복잡하고, 그만큼 많은 것을 제공합니다. 더 좋은 인터페이스"
@@ -6453,8 +6483,9 @@ msgid "A game UI with a health bar, energy bar, bomb and money counters"
 msgstr "체력 막대, 에너지 막대, 폭탄과 돈의 수를 표시하는 게임 UI"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
+#, fuzzy
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -6874,13 +6905,15 @@ msgid "There's no space between the logo and the other UI elements"
 msgstr "로고와 다른 UI 요소들 사이에 공간이 없습니다"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:219
+#, fuzzy
 msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 "오른쪽에 캐릭터가 중앙에 오게 하려면, 우리는 ``CenterContainer`` 를 사용할 겁"
 "니다. ``CenterContainer`` 노드를 ``HBoxContainer`` 의 자식으로 추가하세요. "
@@ -6920,13 +6953,15 @@ msgstr ""
 "UI 레이아웃을 유지하기 위해 다른 두 노드 사이에 새 컨테이너를 배치합니다"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:244
+#, fuzzy
 msgid ""
 "Now we grouped the menu options together, we can tell their container to "
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 "이제 우리는 메뉴 옵션들을 그룹화하여, 그들의 컨테이너를 가능한 많은 수직 공간"
 "을 차지하도록 확장시킬 수 있습니다. ``MenuOptions`` 노드를 선택합니다. 인스펙"
@@ -6982,9 +7017,10 @@ msgstr ""
 "가 있는 게임 사용자 인터페이스를 만들 것입니다."
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
+#, fuzzy
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -8220,8 +8256,9 @@ msgid "Intro"
 msgstr "소개"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
+#, fuzzy
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 "이 튜토리얼에서는 우리는 캐릭터를 체력 막대와 연결하고 체력이 줄어드는 것을 "
@@ -8303,14 +8340,15 @@ msgid "To do this, we will use **signals**."
 msgstr "그러기 위해서, 우리는 **시그널(signals)** 을 사용할 것입니다."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:49
+#, fuzzy
 msgid ""
 "Signals are Godot's version of the Observer pattern. They allow us to send "
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 "시그널은 옵저버 패턴의 Godot 버전입니다. 그들로 메시지를 전달할 수 있습니다. "
@@ -8336,13 +8374,14 @@ msgstr ""
 "zip 파일을 풀고 두 개의 폴더가 나옵니다: `start` 와 `end` 입니다."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
+#, fuzzy
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 "Godot에서 ``start`` 프로젝트를 불러옵니다. ``파일 시스템`` 독에서 "
 "LevelMockup.tscn을 더블 클릭해서 엽니다. 이것은 두 캐릭터가 마주 보고 있는 "
@@ -8376,9 +8415,11 @@ msgid "The scene tree, with the GUI scene set to display its children"
 msgstr "GUI 씬이 자식으로 보이게 놓은 씬 트리"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
+#, fuzzy
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 "GUI 씬은 모든 게임 사용자 인터페이스를 캡슐화 합니다. 씬 안에 존재하는 노드"
 "의 경로를 얻는 스크립트와 함께 제공됩니다:"
@@ -8622,11 +8663,12 @@ msgstr ""
 "용할 수 있습니다."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
+#, fuzzy
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 "이것을 염두해 두고 ``GUI`` 를 ``Player`` 에 연결합시다. 씬 독에서 ``Player`` "
 "노드를 클릭하여 선택합니다. 인스펙터에서 노드(Node) 탭을 클릭합니다. 여기가 "
@@ -8726,21 +8768,23 @@ msgid "Godot writes the callback method for you and takes you to it"
 msgstr "Godot는 콜백 메서드를 적어 사용자에게 전달합니다"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
+#, fuzzy
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 "함수 이름 다음의 괄호 안에, ``player_health`` 인수를 추가하세요. 플레이어가 "
 "``health_changed`` 시그널을 방출할 때 그것을 ``health`` 와 함께 보낼 것입니"
 "다. 코드는 다음과 같아야 합니다:"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
+#, fuzzy
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 "엔진은 파스칼 표기법(PascalCase)을 스네이크 표기법(snake_case)으로 변환하지 "
 "않기 때문에, C# 예제처럼 우리는 공식  `C# 명명 규칙 <https://docs.microsoft."
@@ -8757,8 +8801,9 @@ msgstr ""
 "다"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
+#, fuzzy
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 "``_on_Player_health_changed`` 안에서 ``update_health`` 라는 두 번째 함수를 호"
@@ -8807,9 +8852,10 @@ msgid "set the ``TextureProgress``'s ``value`` to ``new_value``"
 msgstr "``TextureProgress`` 의 ``value`` 를 ``new_value`` 로 설정하는 것"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
+#, fuzzy
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 "``str`` 는 내장 함수로 어느 값을 문자로 변환합니다. ``Number`` 의 ``text`` 속"
@@ -8838,11 +8884,12 @@ msgid "Animate the loss of life with the Tween node"
 msgstr "Tween 노드로 체력이 감소하는 것을 애니메이트하기"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:367
+#, fuzzy
 msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -9040,7 +9087,8 @@ msgstr ""
 "해서, 체력 막대가 더 멋진 방식으로 움직이면 좋을 것입니다."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+#, fuzzy
+msgid "The animation is smooth, but the number is broken"
 msgstr "애니메이션은 부드럽지만 숫자는 그렇지 않습니다"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -9059,7 +9107,8 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr "게임을 다시 실행하면 멋진 블록 애니메이션을 볼 수 있습니다."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+#, fuzzy
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr "animated\\_health를 반올림 해서 일석이조의 효과를 냈습니다"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -9159,10 +9208,11 @@ msgstr ""
 "`modulate` 에서 색상을 사용하여 수정할 수 있습니다."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:611
+#, fuzzy
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 "``modulate`` 는 4 개의 채널로 ``Color`` 값을 갖습니다: 빨강, 초록, 파랑, 그리"
 "고 알파입니다. 처음 세 개의 채널들 중 하나를 어둡게 하면 그것은 인터페이스에"
@@ -9200,8 +9250,9 @@ msgstr ""
 "다:"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
+#, fuzzy
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -9365,10 +9416,11 @@ msgstr ""
 "뜨면 애니메이션 이름을 \"intro\" 라고 적습니다."
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
+#, fuzzy
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 "이제 애니메이션이 있으므로 속성 에디터는 \"애니메이션 편집\" 모드로 들어갑니"
 "다. 이 모드에서, 속성 에디터 평의 모든 속성에 키 아이콘이 나타납니다. Godot에"
@@ -9446,10 +9498,11 @@ msgid "Nodes and resources"
 msgstr "노드와 리소스"
 
 #: ../../docs/getting_started/step_by_step/resources.rst:9
+#, fuzzy
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 "지금까지, :ref:`Nodes <class_Node>` 클래스는  Godot에서 가장 중요한 데이터 형"
@@ -9458,11 +9511,12 @@ msgstr ""
 "<class_Resource>` 입니다."
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
+#, fuzzy
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 "*노드*는 다음과 같은 기능을 제공합니다: 스프라이트를 그려주고 3D 모델링을 해"
 "주며 물리 시뮬레이션을 해주고, 유저 인터페이스 정리 등을 해줍니다.\n"
@@ -9485,10 +9539,11 @@ msgstr ""
 "ref:`Font <class_Font>`, :ref:`Translation <class_Translation>`."
 
 #: ../../docs/getting_started/step_by_step/resources.rst:26
+#, fuzzy
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 "리소스가 디스크에서 불러올 때, **항상 한번만 불러옵니다**. 즉, 메모리에서 이"
@@ -9497,9 +9552,10 @@ msgstr ""
 "없습니다."
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
+#, fuzzy
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -9535,17 +9591,19 @@ msgstr ""
 "<class_Texture>` 가 있습니다:"
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
+#, fuzzy
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr "리소스 미리보기를 클릭해서 리소스를 보고 속성을 편집합니다."
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
+#, fuzzy
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 "경로 속성은 리소스가 어디에서 오는지를 알려줍니다. 이 경우에 리소스는  "
 "``robi.png``\\ 라 부르는 PNG 이미지에서 왔습니다. 리소스가 이와 같은 파일에"
@@ -9624,11 +9682,12 @@ msgstr ""
 "로 반환합니다. 그런 뒤 이것을 다른 노드의 자식으로 추가할 수 있습니다."
 
 #: ../../docs/getting_started/step_by_step/resources.rst:137
+#, fuzzy
 msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 "이 접근은 여러 장점이 있습니다. :ref:`PackedScene.instance() "
@@ -9670,8 +9729,9 @@ msgstr ""
 "계산 메모리 관리를 상속합니다."
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
+#, fuzzy
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -9867,8 +9927,9 @@ msgstr ""
 "추가하는 간단한 플러그인을 제작합니다."
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
+#, fuzzy
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 "CurveTables은 예외로 실수 값의 배열이나 :ref:`Curve <class_Curve>`/:ref:"
@@ -9904,11 +9965,12 @@ msgid "File system"
 msgstr "파일 시스템(File system)"
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:9
+#, fuzzy
 msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 "파일 시스템은 하지만 엔진 개발에 있어 또 다른 주요 주제입니다. 파일 시스템은 "
 "어떻게 에셋이 저장되고 액세스 되는 지를 관리합니다. 잘 설계된 파일 시스템은 "
@@ -9951,10 +10013,11 @@ msgstr ""
 "일로 저장됩니다. 예를 들어, 폰트 리소스는 종종 폰트 텍스쳐와 묶여집니다."
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:30
+#, fuzzy
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 "일반적으로 Godot 파일 시스템은 메타데이터 파일 사용을 피합니다. 그 이유는 간"
@@ -10519,11 +10582,12 @@ msgstr ""
 "을 선택하고 \"오토로드\" 탭으로 갑니다."
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
+#, fuzzy
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 "여기서 원하는 씬이나 스크립트를 추가하실 수 있습니다. 목록에서 각 항목에는 노"
 "드의 ``name`` 속성으로 지정하는 이름이 필요합니다. 글로벌 씬 트리에 추가된 항"
@@ -10878,12 +10942,13 @@ msgstr ""
 "Godot 에디터는 당신이 원하는 씬 에디터 옆에 각 패널을 고정할 수 있습니다."
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:57
+#, fuzzy
 msgid ""
 "While both editors may seem similar, there are many differences below the "
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 "두 에디터가 비슷해 보이지만, 외양 아래에 많은 차이가 있습니다. 둘 다 파일 시"
 "스템을 사용해서 프로젝트를 조직할 수 있지만, Godot의 접근은 하나의 구성 파"
@@ -10993,8 +11058,9 @@ msgstr ""
 "설정함으로써 그들을 연결하도록 구성되어 있습니다."
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
+#, fuzzy
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -11151,13 +11217,14 @@ msgstr ""
 "게 자신의 능력을 제공합니다: 이것이 상속입니다."
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
+#, fuzzy
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 "두 번째로, 씬의 하위 트리를 추출하여 고유의 씬을 만들 수 있습니다, 이걸로 두 "
 "번째와 세 번째 문제에 답할 수 있습니다: 비록 씬 트리가 너무 깊어지더라도, 더 "
@@ -11228,9 +11295,10 @@ msgstr ""
 "만, 이 모두는 프리펩에 의해 정의된 같은 속성을 지닙니다."
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
+#, fuzzy
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -12875,10 +12943,11 @@ msgstr ""
 "위해, Python처럼 인덱스가 음수일 수도 있습니다."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:489
+#, fuzzy
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -13357,8 +13426,9 @@ msgid "Remove ``case``"
 msgstr "``case`` 를 제거하십시오"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
+#, fuzzy
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 "모든 ``break`` 를 제거하십시오. 기본적으로 ``break`` 가 되지 않도록 하고 싶다"
@@ -13448,9 +13518,10 @@ msgstr ""
 "첩 할 수 있습니다."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
+#, fuzzy
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 "배열의 길이가 먼저 테스트 되고, 그것이 패턴과 같은 크기이어야 합니다, 그렇지 "
 "않으면 패턴이 일치하지 않습니다."
@@ -13479,9 +13550,10 @@ msgstr ""
 "배열 패턴과 같은 방식으로 작동합니다. 모든 키는 일정한 패턴이어야 합니다."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
+#, fuzzy
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 "딕셔너리의 크기가 먼저 테스트 되고, 그것이 패턴과 같은 크기이어야 합니다, 그"
 "렇지 않으면 패턴이 일치하지 않습니다."
@@ -13743,11 +13815,12 @@ msgstr ""
 "인수의 형태로 가져야 합니다 (하단을 참고하세요)."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
+#, fuzzy
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 "멤버 변수 내보내기의 기본적인 이점은 에디터에서 보이고 편집할 수 있는 것입니"
 "다. 이 방법으로 아티스트와 게임 디자이너가 프로그램이 실행 방법에 영향을 주"
@@ -13806,8 +13879,9 @@ msgid "Exporting arrays"
 msgstr "배열 내보내기"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
+#, fuzzy
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -13869,8 +13943,9 @@ msgstr ""
 "로 변수를 내보낼 때 특히 유용합니다."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
+#, fuzzy
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 "말한 대로 *로컬* 액세스는 setter와 getter를 트리거 하지 않을 것입니다. 여기"
@@ -13881,9 +13956,10 @@ msgid "Tool mode"
 msgstr "툴 모드"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
+#, fuzzy
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -13968,13 +14044,14 @@ msgid "Coroutines with yield"
 msgstr "yield를 가진 코루틴(Coroutine)"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1520
+#, fuzzy
 msgid ""
 "GDScript offers support for `coroutines <https://en.wikipedia.org/wiki/"
 "Coroutine>`_ via the ``yield`` built-in function. Calling ``yield()`` will "
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 "GDScript ``yield`` 내장 함수를 통해 `coroutines <https://en.wikipedia.org/"
 "wiki/Coroutine>`_ 을 지원합니다. ``yield()`` 를 호출하면 반환 값과 같은 함수"
@@ -13997,9 +14074,10 @@ msgid "Coroutines & signals"
 msgstr "코루틴 & 시그널"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
+#, fuzzy
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 "``yield`` 를 사용하는 진정한 힘은 시그널과 결합될 때 나타납니다. ``yield`` "
@@ -22753,7 +22831,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "도구"
 
@@ -25687,8 +25765,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -25901,9 +25978,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -27894,7 +27971,7 @@ msgstr ":ref:`Sprite <class_Sprite>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
 #, fuzzy
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ":ref:`Color <class_Color>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -28630,437 +28707,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -30826,7 +30472,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -30836,7 +30482,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -46799,9 +46445,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -46851,9 +46497,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -46907,46 +46553,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr "행성 색칠하기"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -46954,7 +46598,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -46963,7 +46607,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -46971,7 +46615,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -46981,7 +46625,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -46992,19 +46636,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -47012,13 +46656,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -47026,7 +46670,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -47035,7 +46679,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -47049,7 +46693,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -47058,7 +46702,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -47066,10 +46710,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -48034,6 +47678,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -50951,6 +50600,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -55497,11 +55572,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -55695,74 +55770,71 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr "프로젝트 설정하기"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 "`godot-cpp 저장소 <https://github.com/GodotNativeTools/godot-cpp>`_ 의 사본."
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -55770,131 +55842,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr "간단한 플러그인 만들기"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -55902,55 +55970,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -55961,22 +56029,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -55985,7 +56053,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -55993,11 +56061,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -56006,42 +56074,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -56051,7 +56126,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -56060,7 +56135,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -56068,58 +56143,256 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+#, fuzzy
+msgid "Adding properties"
+msgstr "노드 속성"
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -58209,7 +58482,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -58217,18 +58490,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -58236,23 +58509,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -58260,35 +58533,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -58297,103 +58570,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -58401,20 +58674,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -58453,11 +58726,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -58467,24 +58752,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -58493,7 +58778,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -58501,18 +58786,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -58522,7 +58807,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -58531,37 +58816,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -58569,63 +58854,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -58633,13 +58918,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -58647,7 +58932,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -58655,25 +58940,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -58681,30 +58966,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -58712,7 +58997,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -58721,25 +59006,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -58750,46 +59035,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -58798,68 +59083,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -58867,7 +59152,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -58876,11 +59161,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -58888,114 +59173,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -59062,37 +59347,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -59100,61 +59385,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -59174,18 +59459,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -59193,11 +59478,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -59205,37 +59490,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -59296,27 +59581,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -59324,24 +59609,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -59349,29 +59621,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -59379,35 +59651,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -59415,40 +59687,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -59456,131 +59728,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -59600,29 +59872,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -59633,17 +59905,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "실행"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -59753,6 +60025,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -59837,61 +60113,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -59900,13 +60176,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -59915,11 +60191,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -59927,14 +60203,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -59942,14 +60218,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -59958,14 +60234,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -59975,7 +60251,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -59984,7 +60260,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -59993,7 +60269,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -60024,7 +60300,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -60034,7 +60310,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -60042,14 +60318,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -60057,21 +60333,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -60080,7 +60356,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -60090,7 +60366,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/lt.po b/weblate/lt.po
index 8ae04aae79..d8bc9c203e 100644
--- a/weblate/lt.po
+++ b/weblate/lt.po
@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-06-12 09:40+0000\n"
 "Last-Translator: Kornelijus <kornelijus.github@gmail.com>\n"
 "Language-Team: Lithuanian <https://hosted.weblate.org/projects/godot-engine/"
@@ -65,9 +65,9 @@ msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 
 #: ../../docs/index.rst:43
@@ -133,7 +133,6 @@ msgstr "Apie"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -152,6 +151,7 @@ msgstr "Apie"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -303,9 +303,9 @@ msgstr ""
 
 #: ../../docs/about/introduction.rst:85
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1246,7 +1246,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1713,7 +1713,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1788,13 +1788,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2038,8 +2038,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2063,7 +2063,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2137,7 +2137,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2151,7 +2151,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2491,6 +2491,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Signalai"
@@ -2961,7 +2962,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3087,7 +3088,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3296,7 +3297,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3394,7 +3395,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3422,7 +3423,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -3920,7 +3921,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -3976,8 +3977,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4053,7 +4054,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4150,7 +4151,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4236,14 +4237,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4352,7 +4353,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4398,7 +4399,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4438,7 +4439,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4479,9 +4480,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4569,7 +4570,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4686,7 +4687,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4734,7 +4735,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4876,7 +4877,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -4984,7 +4985,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5008,7 +5009,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5335,9 +5336,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5367,8 +5369,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5408,8 +5411,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6311,7 +6314,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6380,9 +6383,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6399,12 +6402,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6427,8 +6430,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6604,10 +6608,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6686,16 +6690,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6706,7 +6710,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6748,7 +6752,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6775,7 +6779,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -6924,7 +6928,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -6939,7 +6943,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7017,7 +7021,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7044,7 +7048,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7181,9 +7185,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7252,16 +7256,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7278,14 +7282,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7316,16 +7320,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7387,7 +7391,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7417,7 +7421,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7563,7 +7567,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7593,7 +7597,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7625,7 +7629,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8060,9 +8064,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8372,7 +8376,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8452,7 +8456,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8569,12 +8573,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8626,7 +8630,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10062,7 +10066,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10442,7 +10446,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10521,7 +10525,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10547,7 +10551,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10758,9 +10762,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10805,7 +10809,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10851,7 +10855,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10862,7 +10866,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -10933,7 +10937,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -10953,7 +10957,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19327,7 +19331,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -22261,8 +22265,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22475,9 +22478,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24462,7 +24465,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25193,437 +25196,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27389,7 +26961,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27399,7 +26971,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42692,9 +42264,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42744,9 +42316,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42800,46 +42372,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42847,7 +42417,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42856,7 +42426,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42864,7 +42434,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42874,7 +42444,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -42885,19 +42455,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -42905,13 +42475,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -42919,7 +42489,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -42928,7 +42498,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -42942,7 +42512,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -42951,7 +42521,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -42959,10 +42529,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -43927,6 +43497,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46842,6 +46417,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51386,11 +51387,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51584,73 +51585,70 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51658,131 +51656,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51790,55 +51784,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51849,22 +51843,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51873,7 +51867,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -51881,11 +51875,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -51894,42 +51888,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -51939,7 +51940,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -51948,7 +51949,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -51956,58 +51957,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54097,7 +54295,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54105,18 +54303,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54124,23 +54322,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54148,35 +54346,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54185,103 +54383,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54289,20 +54487,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54341,11 +54539,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54355,24 +54565,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54381,7 +54591,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54389,18 +54599,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54410,7 +54620,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54419,37 +54629,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54457,63 +54667,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54521,13 +54731,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54535,7 +54745,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54543,25 +54753,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54569,30 +54779,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54600,7 +54810,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54609,25 +54819,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54638,46 +54848,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54686,68 +54896,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54755,7 +54965,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54764,11 +54974,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54776,114 +54986,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -54950,37 +55160,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -54988,61 +55198,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55062,18 +55272,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55081,11 +55291,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55093,37 +55303,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55184,27 +55394,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55212,24 +55422,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55237,29 +55434,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55267,35 +55464,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55303,40 +55500,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55344,131 +55541,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55488,29 +55685,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55521,17 +55718,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55641,6 +55838,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55725,61 +55926,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55788,13 +55989,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55803,11 +56004,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55815,14 +56016,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55830,14 +56031,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55846,14 +56047,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55863,7 +56064,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55872,7 +56073,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -55881,7 +56082,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -55912,7 +56113,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -55922,7 +56123,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -55930,14 +56131,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -55945,21 +56146,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -55968,7 +56169,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -55978,7 +56179,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/ms.po b/weblate/ms.po
index 0753d754f8..f5530e55f8 100644
--- a/weblate/ms.po
+++ b/weblate/ms.po
@@ -9,7 +9,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-07-29 04:40+0000\n"
 "Last-Translator: Nafis Ibrahim <thepreciousnafis@gmail.com>\n"
 "Language-Team: Malay <https://hosted.weblate.org/projects/godot-engine/godot-"
@@ -75,13 +75,14 @@ msgstr ""
 "memberitahu kami!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Hantarkan isu atau tarik permintaan pada 'repositori GitHub <https://github."
 "com/godotengine/godot-docs/issues>'_, tolong kami 'terjemah dokumentasi ini "
@@ -155,7 +156,6 @@ msgstr "Tentang"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -174,6 +174,7 @@ msgstr "Tentang"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -327,9 +328,9 @@ msgstr ""
 
 #: ../../docs/about/introduction.rst:85
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1270,7 +1271,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1737,7 +1738,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1812,13 +1813,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2062,8 +2063,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2087,7 +2088,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2161,7 +2162,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2175,7 +2176,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2515,6 +2516,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr ""
@@ -2985,7 +2987,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3111,7 +3113,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3321,7 +3323,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3419,7 +3421,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3447,7 +3449,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -3946,7 +3948,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4002,8 +4004,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4080,7 +4082,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4177,7 +4179,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4263,14 +4265,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4379,7 +4381,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4425,7 +4427,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4465,7 +4467,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4506,9 +4508,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4596,7 +4598,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4713,7 +4715,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4761,7 +4763,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4903,7 +4905,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5011,7 +5013,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5035,7 +5037,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5362,9 +5364,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5394,8 +5397,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5435,8 +5439,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6340,8 +6344,9 @@ msgid "Intro"
 msgstr "Pengenalan"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
+#, fuzzy
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 "Dalam tutorial ini anda akan menghubungkan watak kepada bar nyawa dan "
@@ -6412,9 +6417,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6431,12 +6436,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6459,8 +6464,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6636,10 +6642,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6718,16 +6724,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6738,7 +6744,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6780,7 +6786,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6807,7 +6813,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -6956,7 +6962,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -6971,7 +6977,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7049,7 +7055,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7076,7 +7082,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7213,9 +7219,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7284,16 +7290,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7310,14 +7316,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7348,16 +7354,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7419,7 +7425,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7449,7 +7455,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7595,7 +7601,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7625,7 +7631,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7657,7 +7663,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8092,9 +8098,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8403,7 +8409,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8483,7 +8489,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8600,12 +8606,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8657,7 +8663,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10093,7 +10099,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10473,7 +10479,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10552,7 +10558,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10578,7 +10584,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10789,9 +10795,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10836,7 +10842,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10882,7 +10888,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10893,7 +10899,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -10964,7 +10970,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -10984,7 +10990,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19362,7 +19368,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -22296,8 +22302,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22510,9 +22515,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24497,7 +24502,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25228,437 +25233,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27424,7 +26998,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27434,7 +27008,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42728,9 +42302,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42780,9 +42354,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42836,46 +42410,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42883,7 +42455,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42892,7 +42464,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42900,7 +42472,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42910,7 +42482,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -42921,19 +42493,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -42941,13 +42513,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -42955,7 +42527,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -42964,7 +42536,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -42978,7 +42550,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -42987,7 +42559,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -42995,10 +42567,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -43963,6 +43535,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46878,6 +46455,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51422,11 +51425,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51620,73 +51623,70 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51694,131 +51694,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51826,55 +51822,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51885,22 +51881,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51909,7 +51905,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -51917,11 +51913,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -51930,42 +51926,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -51975,7 +51978,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -51984,7 +51987,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -51992,58 +51995,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54134,7 +54334,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54142,18 +54342,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54161,23 +54361,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54185,35 +54385,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54222,103 +54422,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54326,20 +54526,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54378,11 +54578,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54392,24 +54604,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54418,7 +54630,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54426,18 +54638,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54447,7 +54659,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54456,37 +54668,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54494,63 +54706,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54558,13 +54770,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54572,7 +54784,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54580,25 +54792,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54606,30 +54818,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54637,7 +54849,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54646,25 +54858,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54675,46 +54887,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54723,68 +54935,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54792,7 +55004,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54801,11 +55013,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54813,114 +55025,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -54987,37 +55199,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55025,61 +55237,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55099,18 +55311,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55118,11 +55330,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55130,37 +55342,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55221,27 +55433,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55249,24 +55461,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55274,29 +55473,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55304,35 +55503,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55340,40 +55539,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55381,131 +55580,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55525,29 +55724,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55558,17 +55757,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55678,6 +55877,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55762,61 +55965,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55825,13 +56028,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55840,11 +56043,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55852,14 +56055,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55867,14 +56070,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55883,14 +56086,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55900,7 +56103,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55909,7 +56112,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -55918,7 +56121,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -55949,7 +56152,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -55959,7 +56162,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -55967,14 +56170,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -55982,21 +56185,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56005,7 +56208,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56015,7 +56218,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/nb.po b/weblate/nb.po
index 60eab1a204..e640b00cbc 100644
--- a/weblate/nb.po
+++ b/weblate/nb.po
@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-06-22 19:42+0000\n"
 "Last-Translator: Frank T. Rambol <frank@d-fect.com>\n"
 "Language-Team: Norwegian Bokmål <https://hosted.weblate.org/projects/godot-"
@@ -63,9 +63,9 @@ msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 
 #: ../../docs/index.rst:43
@@ -131,7 +131,6 @@ msgstr ""
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -150,6 +149,7 @@ msgstr ""
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -294,9 +294,9 @@ msgstr ""
 
 #: ../../docs/about/introduction.rst:85
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1237,7 +1237,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1704,7 +1704,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1779,13 +1779,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2029,8 +2029,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2054,7 +2054,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2128,7 +2128,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2142,7 +2142,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2482,6 +2482,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Signaler"
@@ -2952,7 +2953,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3078,7 +3079,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3287,7 +3288,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3385,7 +3386,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3413,7 +3414,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -3911,7 +3912,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -3967,8 +3968,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4044,7 +4045,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4141,7 +4142,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4227,14 +4228,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4343,7 +4344,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4389,7 +4390,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4429,7 +4430,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4470,9 +4471,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4560,7 +4561,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4677,7 +4678,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4725,7 +4726,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4867,7 +4868,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -4975,7 +4976,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -4999,7 +5000,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5326,9 +5327,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5358,8 +5360,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5399,8 +5402,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6302,7 +6305,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6371,9 +6374,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6390,12 +6393,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6418,8 +6421,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6595,10 +6599,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6677,16 +6681,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6697,7 +6701,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6739,7 +6743,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6766,7 +6770,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -6915,7 +6919,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -6930,7 +6934,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7008,7 +7012,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7035,7 +7039,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7172,9 +7176,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7243,16 +7247,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7269,14 +7273,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7307,16 +7311,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7378,7 +7382,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7408,7 +7412,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7554,7 +7558,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7584,7 +7588,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7616,7 +7620,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8051,9 +8055,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8363,7 +8367,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8443,7 +8447,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8560,12 +8564,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8617,7 +8621,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10053,7 +10057,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10433,7 +10437,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10512,7 +10516,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10538,7 +10542,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10749,9 +10753,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10796,7 +10800,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10842,7 +10846,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10853,7 +10857,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -10924,7 +10928,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -10944,7 +10948,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19318,7 +19322,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -22252,8 +22256,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22466,9 +22469,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24453,7 +24456,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25184,437 +25187,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27380,7 +26952,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27390,7 +26962,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42683,9 +42255,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42735,9 +42307,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42791,46 +42363,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42838,7 +42408,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42847,7 +42417,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42855,7 +42425,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42865,7 +42435,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -42876,19 +42446,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -42896,13 +42466,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -42910,7 +42480,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -42919,7 +42489,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -42933,7 +42503,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -42942,7 +42512,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -42950,10 +42520,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -43918,6 +43488,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46833,6 +46408,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51377,11 +51378,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51575,73 +51576,70 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51649,131 +51647,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51781,55 +51775,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51840,22 +51834,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51864,7 +51858,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -51872,11 +51866,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -51885,42 +51879,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -51930,7 +51931,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -51939,7 +51940,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -51947,58 +51948,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54088,7 +54286,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54096,18 +54294,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54115,23 +54313,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54139,35 +54337,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54176,103 +54374,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54280,20 +54478,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54332,11 +54530,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54346,24 +54556,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54372,7 +54582,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54380,18 +54590,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54401,7 +54611,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54410,37 +54620,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54448,63 +54658,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54512,13 +54722,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54526,7 +54736,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54534,25 +54744,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54560,30 +54770,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54591,7 +54801,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54600,25 +54810,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54629,46 +54839,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54677,68 +54887,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54746,7 +54956,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54755,11 +54965,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54767,114 +54977,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -54941,37 +55151,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -54979,61 +55189,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55053,18 +55263,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55072,11 +55282,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55084,37 +55294,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55175,27 +55385,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55203,24 +55413,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55228,29 +55425,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55258,35 +55455,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55294,40 +55491,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55335,131 +55532,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55479,29 +55676,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55512,17 +55709,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55632,6 +55829,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55716,61 +55917,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55779,13 +55980,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55794,11 +55995,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55806,14 +56007,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55821,14 +56022,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55837,14 +56038,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55854,7 +56055,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55863,7 +56064,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -55872,7 +56073,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -55903,7 +56104,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -55913,7 +56114,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -55921,14 +56122,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -55936,21 +56137,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -55959,7 +56160,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -55969,7 +56170,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/nl.po b/weblate/nl.po
index b29aba3fa9..d3b686f7ab 100644
--- a/weblate/nl.po
+++ b/weblate/nl.po
@@ -16,7 +16,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-12-04 22:23+0000\n"
 "Last-Translator: Laurent Windels <laurentwindels@yahoo.com>\n"
 "Language-Team: Dutch <https://hosted.weblate.org/projects/godot-engine/godot-"
@@ -81,13 +81,14 @@ msgstr ""
 "dan de documentatie te verbeteren door het ons te laten weten!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Rapporteer een probleem of maak een \"pull\" verzoek op de `GitHub "
 "repository <https://github.com/godotengine/godot-docs/issues>`_, help ons "
@@ -162,7 +163,6 @@ msgstr "Over"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -181,6 +181,7 @@ msgstr "Over"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -383,10 +384,11 @@ msgstr ""
 "de engine, ontwikkelen van C++ modules of editor plugins."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1367,7 +1369,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1834,7 +1836,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1909,13 +1911,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2159,8 +2161,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2184,7 +2186,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2258,7 +2260,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2272,7 +2274,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2612,6 +2614,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr ""
@@ -3082,7 +3085,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3208,7 +3211,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3418,7 +3421,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3516,7 +3519,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3544,7 +3547,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -4042,7 +4045,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4098,8 +4101,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4175,7 +4178,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4272,7 +4275,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4358,14 +4361,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4474,7 +4477,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4520,7 +4523,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4560,7 +4563,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4601,9 +4604,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4691,7 +4694,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4808,7 +4811,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4856,7 +4859,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4998,7 +5001,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5106,7 +5109,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5130,7 +5133,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5457,9 +5460,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5489,8 +5493,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5530,8 +5535,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6433,7 +6438,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6502,9 +6507,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6521,12 +6526,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6549,8 +6554,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6726,10 +6732,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6808,16 +6814,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6828,7 +6834,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6870,7 +6876,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6897,7 +6903,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -7046,7 +7052,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7061,7 +7067,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7139,7 +7145,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7166,7 +7172,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7303,9 +7309,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7374,16 +7380,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7400,14 +7406,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7438,16 +7444,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7509,7 +7515,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7539,7 +7545,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7685,7 +7691,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7715,7 +7721,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7747,7 +7753,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8182,9 +8188,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8493,7 +8499,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8573,7 +8579,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8690,12 +8696,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8747,7 +8753,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10183,7 +10189,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10563,7 +10569,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10642,7 +10648,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10668,7 +10674,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10879,9 +10885,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10926,7 +10932,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10972,7 +10978,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10983,7 +10989,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11054,7 +11060,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11074,7 +11080,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19447,7 +19453,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -22381,8 +22387,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22595,9 +22600,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24582,7 +24587,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25313,437 +25318,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27509,7 +27083,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27519,7 +27093,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42812,9 +42386,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42864,9 +42438,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42920,46 +42494,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42967,7 +42539,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42976,7 +42548,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42984,7 +42556,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42994,7 +42566,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -43005,19 +42577,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -43025,13 +42597,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43039,7 +42611,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43048,7 +42620,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43062,7 +42634,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43071,7 +42643,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43079,10 +42651,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44047,6 +43619,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46962,6 +46539,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51506,11 +51509,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51704,73 +51707,70 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51778,131 +51778,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51910,55 +51906,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51969,22 +51965,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51993,7 +51989,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -52001,11 +51997,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -52014,42 +52010,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52059,7 +52062,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52068,7 +52071,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52076,58 +52079,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54217,7 +54417,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54225,18 +54425,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54244,23 +54444,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54268,35 +54468,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54305,103 +54505,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54409,20 +54609,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54461,11 +54661,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54475,24 +54687,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54501,7 +54713,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54509,18 +54721,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54530,7 +54742,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54539,37 +54751,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54577,63 +54789,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54641,13 +54853,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54655,7 +54867,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54663,25 +54875,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54689,30 +54901,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54720,7 +54932,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54729,25 +54941,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54758,46 +54970,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54806,68 +55018,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54875,7 +55087,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54884,11 +55096,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54896,114 +55108,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55070,37 +55282,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55108,61 +55320,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55182,18 +55394,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55201,11 +55413,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55213,37 +55425,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55304,27 +55516,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55332,24 +55544,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55357,29 +55556,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55387,35 +55586,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55423,40 +55622,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55464,131 +55663,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55608,29 +55807,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55641,17 +55840,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55761,6 +55960,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55845,61 +56048,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55908,13 +56111,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55923,11 +56126,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55935,14 +56138,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55950,14 +56153,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55966,14 +56169,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55983,7 +56186,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55992,7 +56195,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -56001,7 +56204,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56032,7 +56235,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56042,7 +56245,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56050,14 +56253,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56065,21 +56268,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56088,7 +56291,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56098,7 +56301,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/pl.po b/weblate/pl.po
index 1499b18092..e2954a37d3 100644
--- a/weblate/pl.po
+++ b/weblate/pl.po
@@ -25,7 +25,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-12-04 22:23+0000\n"
 "Last-Translator: Tomek <kobewi4e@gmail.com>\n"
 "Language-Team: Polish <https://hosted.weblate.org/projects/godot-engine/"
@@ -91,13 +91,14 @@ msgstr ""
 "tym!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Zgłoś problem lub wgraj zmiane w naszym `repozytorium GitHub <https://github."
 "com/godotengine/godot-docs/issues>`_, pomóż nam `przetłumaczyć dokumentacje "
@@ -169,7 +170,6 @@ msgstr "O silniku"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -188,6 +188,7 @@ msgstr "O silniku"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -387,10 +388,11 @@ msgstr ""
 "silnika, tworznenia modułów C++ lub wtyczek edytora."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1610,7 +1612,7 @@ msgstr "Może być rozbudowywany (aby mieć więcej funkcji)."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
 #, fuzzy
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr "Może być dodany do innych węzłów jako jego dziecko."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -2231,13 +2233,14 @@ msgstr ""
 "własnościowych."
 
 #: ../../docs/getting_started/step_by_step/instancing_continued.rst:43
+#, fuzzy
 msgid ""
 "A lot of time spent in programming games (or software in general) is on "
 "designing an architecture and fitting game components to that architecture. "
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 "Wiele czasu spędzanego w grach (lub ogólnie w oprogramowaniu) to "
@@ -2345,16 +2348,18 @@ msgstr ""
 "wspierane i możliwość dynamicznego dodawania dodatkowych języków skryptowych!"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
+#, fuzzy
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 "Jest to wspaniałe, głównie ze względu na dużą elastyczność, ale również "
 "utrudnia naszą pracę w zakresie języków pomocniczych."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
+#, fuzzy
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2665,9 +2670,10 @@ msgstr ""
 "ustawienie języka skryptu, nazwy klasy i innych opcji."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
+#, fuzzy
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 "W skrypcie GDScript sam plik reprezentuje klasę, więc pole nazwy klasy nie "
 "jest edytowalne."
@@ -2698,9 +2704,10 @@ msgstr ""
 "skryptu pod Inspektorem:"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
+#, fuzzy
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 "Aby edytować skrypt, wybierz jeden z tych przycisków, które są podświetlone "
@@ -2798,11 +2805,12 @@ msgstr ""
 "NodePath) oraz nazwa metody, którą chcesz wykonać."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:205
+#, fuzzy
 msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 "W lewym górnym rogu wyświetlana jest lista węzłów sceny, a nazwa węzła "
 "emitującego jest podświetlona na czerwono. Wybierz tutaj węzeł \"Panel\". Po "
@@ -2823,9 +2831,10 @@ msgstr ""
 "wygeneruje funkcję przed nawiązaniem połączenia."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
+#, fuzzy
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 "I na tym kończy się przewodnik, jak korzystać z interfejsu wizualnego. Jest "
@@ -3255,6 +3264,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Sygnały"
@@ -3820,10 +3830,11 @@ msgstr ""
 "jest dobrym momentem, aby ustalić rozmiar okna gry:"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:198
+#, fuzzy
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 "Teraz możemy użyć funkcji ``_process()`` do zdefiniowania, co gracz będzie "
 "robił. ``_process()`` jest wywoływany co każda klatkę, więc użyjemy go do "
@@ -3994,10 +4005,11 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:372
+#, fuzzy
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 "Odtwórz scenę ponownie i sprawdź, czy animacje są poprawne w każdym z "
 "kierunków. Jeśli jesteś pewien, że ruch działa poprawnie, dodaj ten wiersz "
@@ -4281,8 +4293,9 @@ msgid "See :ref:`doc_instancing` to learn more about instancing."
 msgstr "Zobacz :ref:`doc_instancing` aby dowiedzieć się więcej o instancjach."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
+#, fuzzy
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 "Teraz dodaj następujące węzły jako dzieci ``Main`` i nazwij je tak, jak "
@@ -4415,8 +4428,9 @@ msgid "Main script"
 msgstr "Główny skrypt"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
+#, fuzzy
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 "Dodaj skrypt do ``Main``. W górnej części skryptu używamy ``export "
@@ -4458,8 +4472,9 @@ msgstr ""
 "o 1."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
+#, fuzzy
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -5095,7 +5110,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -5152,8 +5167,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -5256,8 +5271,9 @@ msgstr ""
 "urządzeniem."
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
+#, fuzzy
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 "Następnie utwórz debug keystore, uruchamiając poniższe polecenie w wierszu "
@@ -5384,9 +5400,10 @@ msgstr ""
 "pliki:"
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
+#, fuzzy
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -5502,9 +5519,10 @@ msgid "On top of that, you can **inherit** from any scene."
 msgstr "Ponadto można **dziedziczyć** z każdej sceny."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
+#, fuzzy
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
@@ -5514,8 +5532,9 @@ msgstr ""
 "używając tylko kodu."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
+#, fuzzy
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -5675,9 +5694,10 @@ msgstr ""
 "dostarczane jako wtyczki innych producentów."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
+#, fuzzy
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -5736,7 +5756,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -5772,11 +5792,12 @@ msgid "Design interfaces with the Control nodes"
 msgstr "Twórz interfejs z węzłami kontrolującymi"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:6
+#, fuzzy
 msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -5832,9 +5853,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -5931,7 +5952,7 @@ msgstr "TextureRect"
 #, fuzzy
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 "W interfejsie użytkownika **TextureRect** wyświetla teksturę lub obraz. "
@@ -6056,7 +6077,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -6110,7 +6131,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -6256,7 +6277,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -6367,9 +6388,10 @@ msgstr ""
 "GridContainer z 2 kolumnami. Automatycznie ustawia szerokość każdej z kolumn."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
+#, fuzzy
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 "System UI Godota jest złożony i ma o wiele więcej do zaoferowania. Aby "
@@ -6398,8 +6420,9 @@ msgid "A game UI with a health bar, energy bar, bomb and money counters"
 msgstr "UI gry z paskiem życia, energii, licznikiem bomb i monet"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
+#, fuzzy
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -6774,9 +6797,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -6810,8 +6834,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -6859,8 +6884,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -7817,8 +7842,9 @@ msgid "Intro"
 msgstr "Wstęp"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
+#, fuzzy
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 "W tym poradniku, połączymy postać z paskiem życia i zanimujemy utratę "
@@ -7893,9 +7919,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -7912,12 +7938,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -7940,8 +7966,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -8146,11 +8173,12 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
+#, fuzzy
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 "Mając to na uwadze, podłączmy ``GUI`` do ``Player``. Kliknij na węzeł "
 "``Player``, aby go wybrać. Przejdź do Inspektora i kliknij zakładkę Węzeł. "
@@ -8243,16 +8271,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -8264,8 +8292,9 @@ msgstr ""
 "swoją wartość zdrowia"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
+#, fuzzy
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 "Wewnątrz ``_on_Player_health_changed`` wywołajmy drugą funkcję zwaną "
@@ -8315,7 +8344,7 @@ msgstr "ustaw ``TextureProgress`` ``value``(wartość) na ``new_value``"
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -8348,7 +8377,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -8502,7 +8531,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -8517,7 +8546,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -8598,7 +8627,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -8625,7 +8654,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -8788,10 +8817,11 @@ msgstr ""
 "się okno dialogowe, nazwij animację \"Intro\"."
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
+#, fuzzy
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 "Teraz, gdy mamy animację, edytor właściwości wchodzi w tryb \"edycji animacji"
 "\". W tym trybie obok każdej właściwości edytora właściwości pojawia się "
@@ -8871,16 +8901,16 @@ msgstr "Węzły i zasoby"
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -8903,7 +8933,7 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 "W przypadku wczytania zasobu z dysku **jest on zawsze wczytywany raz**. "
@@ -8916,7 +8946,7 @@ msgstr ""
 #, fuzzy
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -8955,7 +8985,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 #, fuzzy
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 "Kliknięcie zmiennej prawym przyciskiem myszy umożliwi skonfigurowanie jej "
@@ -8963,10 +8993,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -9040,7 +9070,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 "Podejście to ma kilka zalet. Ponieważ funkcja :ref:`PackedScene.instance() "
@@ -9083,7 +9113,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -9230,7 +9260,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -9261,7 +9291,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 "Systemy plików to kolejny gorący temat w rozwoju silnika. System plików "
 "zarządza sposobem przechowywania i dostępu do zasobów. Dobrze zaprojektowany "
@@ -9310,7 +9340,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 "Ogólnie rzecz biorąc, system plików Godot unika stosowania plików "
@@ -9830,9 +9860,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -10180,7 +10210,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 "Oba edytory mogą wydawać się podobne, ale pod maską skrywają wiele różnic. "
 "Obydwa pozwalają zorganizować projekt przy użyciu systemu plików, ale "
@@ -10305,7 +10335,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 #, fuzzy
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -10465,12 +10495,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -10536,9 +10566,10 @@ msgstr ""
 "wszystkie mają te same właściwości, co prefab."
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
+#, fuzzy
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -12206,7 +12237,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -12617,7 +12648,7 @@ msgstr "Usuń ``case``"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -12702,7 +12733,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -12728,7 +12759,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -12961,11 +12992,12 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
+#, fuzzy
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 "Jedną z podstawowych korzyści płynących z eksportowania zmiennych jest ich "
 "widoczność i możliwość edycji w edytorze. W ten sposób artyści i projektanci "
@@ -13019,7 +13051,7 @@ msgstr "Eksportowanie tablic"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -13078,7 +13110,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -13087,9 +13119,10 @@ msgid "Tool mode"
 msgstr "Tryb narzędziowy"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
+#, fuzzy
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -13176,7 +13209,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -13197,7 +13230,7 @@ msgstr "Współprogramy i sygnały"
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -22472,7 +22505,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr "Uruchommy to znowu! Tym razem, obraca się prawidłowo!"
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "Narzędzia"
 
@@ -25520,8 +25553,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -25734,9 +25766,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -27779,7 +27811,7 @@ msgstr ":ref:`String <class_String>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
 #, fuzzy
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ":ref:`Color <class_Color>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -28516,440 +28548,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-#, fuzzy
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-"Jak widać, ta scena ma węzeł :ref:`class_Spatial` jako swój korzeń oraz "
-"wiele dzieci węzłów :ref:`class_MeshInstance`."
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr "Samouczek FPS"
@@ -30980,7 +30578,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -30990,7 +30588,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -46651,9 +46249,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -46703,9 +46301,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -46760,50 +46358,48 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 #, fuzzy
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 "Aby odtworzyć dźwięk strzelającego karabinu, dodaj poniższy kod na końcu "
 "``fire_weapon``:"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 #, fuzzy
 msgid "Coloring the planet"
 msgstr "Konfigurowanie projektu"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -46811,7 +46407,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -46820,7 +46416,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -46828,7 +46424,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -46838,7 +46434,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -46849,21 +46445,21 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 #, fuzzy
 msgid "And now the planet looks like:"
 msgstr "I tak to wygląda w przypadku 3D:"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 #, fuzzy
 msgid "Making an ocean"
 msgstr "Tworzenie zmian"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -46871,13 +46467,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -46885,7 +46481,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -46894,7 +46490,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -46908,7 +46504,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -46917,7 +46513,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -46925,10 +46521,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -47902,6 +47498,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -50842,6 +50443,435 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+#, fuzzy
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+"Jak widać, ta scena ma węzeł :ref:`class_Spatial` jako swój korzeń oraz "
+"wiele dzieci węzłów :ref:`class_MeshInstance`."
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr "Sieć"
@@ -55521,11 +55551,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr "Kompilowanie"
 
@@ -55720,51 +55750,45 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 #, fuzzy
 msgid "Setting up the project"
 msgstr "Tworzenie nowego projektu"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 #, fuzzy
 msgid "a Godot 3.x executable,"
 msgstr "Plik wykonywalny Godota 3.x"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 #, fuzzy
 msgid "a C++ compiler,"
 msgstr "Kompilator C++"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 #, fuzzy
 msgid "SCons as a build tool,"
 msgstr "SCons build system"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-#, fuzzy
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-"Skopiuj to repozytorium: https://github.com/GodotNativeTools/godot_headers"
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -55772,29 +55796,30 @@ msgid ""
 msgstr ""
 "Skopiuj to repozytorium: https://github.com/GodotNativeTools/godot_headers"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -55802,132 +55827,128 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 #, fuzzy
 msgid "Creating a simple plugin"
 msgstr "Tworzenie nowego projektu"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -55935,57 +55956,57 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 #, fuzzy
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 "Zacznij od zadeklarowania zmiennych, których ten obiekt będzie potrzebował:"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -55996,22 +56017,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -56020,7 +56041,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -56028,12 +56049,12 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 #, fuzzy
 msgid "Compiling the plugin"
 msgstr "Kompilowanie naszej wtyczki"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -56042,43 +56063,50 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 #, fuzzy
 msgid "Using the GDNative module"
 msgstr "Używanie twojego modułu GDNative"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -56088,7 +56116,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -56097,7 +56125,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -56105,58 +56133,256 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+#, fuzzy
+msgid "Adding properties"
+msgstr "Właściwości węzła"
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr "Kolejne kroki"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -58261,7 +58487,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -58269,18 +58495,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr "Wybór platformy"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -58288,23 +58514,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -58312,35 +58538,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr "Przykład użycia 4 rdzeni:"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -58349,103 +58575,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr "Bity"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr "**32**: Budowanie binariów dla platform 32-bitowych."
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr "**64**: Budowanie binariów dla platform 64-bitowych."
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr "Inne opcje budowania"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -58453,20 +58679,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -58507,11 +58733,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr "System budowania `SCons <https://www.scons.org>`__."
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr "Ustawianie SCons"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -58521,24 +58759,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr "Ustawianie Pywin32"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -58547,7 +58785,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -58555,18 +58793,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -58576,7 +58814,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -58585,17 +58823,17 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr "Pobieranie kodu źródłowego dla Godota"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
@@ -58605,20 +58843,20 @@ msgstr ""
 "udostępniany na Githubie. Pobranie go (sklonowanie) poprzez Git `Git "
 "<https://git-scm.com/>`__ jest rekomendowane."
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -58626,63 +58864,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -58690,13 +58928,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -58704,7 +58942,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -58712,25 +58950,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr "Na przykład:"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -58738,30 +58976,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr "Uruchamianie SCons"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -58769,7 +59007,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -58778,25 +59016,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -58807,46 +59045,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr "Visual Studio 2013 jest w folderze \"Microsoft Visual Studio 12.0\"."
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr "Visual Studio 2015 jest w folderze \"Microsoft Visual Studio 14.0\"."
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr "itp."
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -58855,68 +59093,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr "x86 (32-bit cl.exe kompilowane dla systemów 32 bitowych)"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr "amd64 (64-bit cl.exe kompilowane dla systemów 64 bitowych)"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr "x86_amd64 (32-bit cl.exe kompilowane dla systemów 64 bitowych)"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr "amd64_x86 (64-bit cl.exe kompilowane dla systemów 32 bitowych)"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr "i po tym możesz uruchomić SCons:"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr "Tworzone w Visual Studio albo innym IDE"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -58924,7 +59162,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -58933,11 +59171,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -58945,114 +59183,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr "**Arch**"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr "**Debian** / **Ubuntu**"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr "**Fedora**"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr "**macOS**"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr "**Mageia**"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr "I dla 64-bitów:"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -59121,37 +59359,37 @@ msgstr "*Opcjonalne* - libudev (budowane z ``udev=yes``)"
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr "*Opcjonalne* - yasm (dla opymalizacji WebM SIMD)"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr "**FreeBSD**"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr "**Gentoo**"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr "**OpenBSD**"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr "**openSUSE**"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr "**Solus**"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -59159,63 +59397,63 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 "Jeśli chcesz możesz skompilować to używając Clang zamiast GCC, używając "
 "następujących komend:"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr "(32 bity)"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr "(64 bity)"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -59236,18 +59474,18 @@ msgstr "Python 2.7+ lub Python 3.5+"
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr "Xcode (albo lżejsza)"
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr "Kompilowanie 32 i 64 bity"
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -59255,11 +59493,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -59267,37 +59505,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -59358,27 +59596,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr "Ustawianie systemu budowania"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -59386,24 +59624,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -59411,29 +59636,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr "Szybsza kompilacja"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -59441,35 +59666,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr "Dodanie wsparcia dla urządzeń x86"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr "To stworzy większy o 6MB plik APK, działający na obu platformach."
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr "Używanie szablonów eksportu"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -59477,43 +59702,43 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr "Instalowanie szablonu"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 #, fuzzy
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates``"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 #, fuzzy
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr "Linux: ``/home/[username]/.local/share/godot/templates/[gd-version]/``"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 #, fuzzy
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr "macOS: ``/users/[username]/.godot/templates``"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -59521,131 +59746,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr "Aplikacja nie zainstalowana"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr "Aplikacja wyłącza się natychmiast"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr "Błąd kompilacji"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -59665,31 +59890,31 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 "Otwórz terminal, przejdź do głównego katalogu kodu źródłowego silnika i "
 "wpisz:"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr "Możesz również uruchomić"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -59700,17 +59925,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "Uruchom"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -59820,6 +60045,10 @@ msgstr "Wypakuj iOS SDK:"
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -59904,61 +60133,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr "Tworzenie szablonów eksportu dla UWP"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr "Powtórz dla innych architektur sprzętowych."
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -59967,13 +60196,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -59982,11 +60211,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr "Uruchamianie aplikacji UWP w Visual Studio"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -59994,14 +60223,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -60009,14 +60238,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -60025,14 +60254,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -60042,7 +60271,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -60051,7 +60280,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -60060,7 +60289,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -60093,7 +60322,7 @@ msgstr "`Python 2.7+ lub Python 3.5+ <https://www.python.org/>`__"
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr "System budowania `SCons <https://www.scons.org>`__"
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -60103,7 +60332,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -60111,14 +60340,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -60126,21 +60355,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -60149,7 +60378,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -60159,7 +60388,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
@@ -67086,6 +67315,13 @@ msgstr ""
 "`Zeef Godot Engine: Prowadzony przez Andre Schmitza katalog zasobów <https://"
 "godot-engine.zeef.com/andre.antonio.schmitz>`_"
 
+#, fuzzy
+#~ msgid ""
+#~ "a copy of the `godot_headers repository <https://github.com/"
+#~ "GodotNativeTools/godot_headers>`_,"
+#~ msgstr ""
+#~ "Skopiuj to repozytorium: https://github.com/GodotNativeTools/godot_headers"
+
 #, fuzzy
 #~ msgid ""
 #~ "NOTE: The result of these operations depends on the operands types. If "
diff --git a/weblate/pt_BR.po b/weblate/pt_BR.po
index 07f700fcc8..6bab1135e7 100644
--- a/weblate/pt_BR.po
+++ b/weblate/pt_BR.po
@@ -71,7 +71,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-12-04 22:23+0000\n"
 "Last-Translator: Julio Yagami <juliohenrique31501234@hotmail.com>\n"
 "Language-Team: Portuguese (Brazil) <https://hosted.weblate.org/projects/"
@@ -136,13 +136,14 @@ msgstr ""
 "nos ajude colaborando para deixar a documentação ainda mais completa!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Envie seu problema ou \"pull request\" no `repositório GitHub <https://"
 "github.com/godotengine/godot-docs/issues>`_, ajude-nos a `traduzir a "
@@ -215,7 +216,6 @@ msgstr "Sobre"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -234,6 +234,7 @@ msgstr "Sobre"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -433,10 +434,11 @@ msgstr ""
 "desenvolvimento de módulos em C++, ou plugins para o editor."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1688,7 +1690,8 @@ msgid "It can be extended (to have more functions)."
 msgstr "Pode ser estendido (ter mais funções)."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+#, fuzzy
+msgid "It can be added to another node as a child."
 msgstr "Pode ser adicionado a outros nós como filho."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -2308,13 +2311,14 @@ msgstr ""
 "(seja por código ou diretamente pelo editor) para as relações de posse."
 
 #: ../../docs/getting_started/step_by_step/instancing_continued.rst:43
+#, fuzzy
 msgid ""
 "A lot of time spent in programming games (or software in general) is on "
 "designing an architecture and fitting game components to that architecture. "
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 "Muito do tempo gasto em programação de jogos (ou de softwares em geral) é "
@@ -2424,16 +2428,18 @@ msgstr ""
 "a habilidade de adicionar linguagens de roteirização extras dinamicamente!"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
+#, fuzzy
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 "Isso é ótimo, principalmente por causa da enorme flexibilidade oferecida, "
 "mas também dificulta nosso trabalho de dar suporte a linguagens."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
+#, fuzzy
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2752,9 +2758,10 @@ msgstr ""
 "relevantes."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
+#, fuzzy
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 "Na GDScript, o arquivo em si representa a classe, então o campo de nome da "
 "classe não é editável."
@@ -2785,9 +2792,10 @@ msgstr ""
 "Script no Inspetor:"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
+#, fuzzy
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 "Para editar o roteiro, selecione um desses botões, ambos destacados na "
@@ -2888,11 +2896,12 @@ msgstr ""
 "método a ser disparado."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:205
+#, fuzzy
 msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 "A seção superior esquerda mostra uma lista com nós da sua cena, com o nome "
 "do nó emissor destacado em vermelho. Selecione o nó \"Painel\" aqui. Quando "
@@ -2912,9 +2921,10 @@ msgstr ""
 "para você antes de configurar a conexão."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
+#, fuzzy
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 "E isso conclui o guia sobre como usar a interface visual. Entretanto, isso é "
@@ -3380,6 +3390,7 @@ msgstr "Apenas GDScript pode criar variáveis globais para cada script nomeado."
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Sinais"
@@ -4036,10 +4047,11 @@ msgstr ""
 "uma boa hora para descobrir o tamanho da janela do jogo:"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:198
+#, fuzzy
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 "Agora podemos usar a função ``_process()`` para definir o que o jogador "
 "fará. ``_process()`` é chamada a cada quadro, então usaremos isso para "
@@ -4219,10 +4231,11 @@ msgstr ""
 "acima:"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:372
+#, fuzzy
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 "Rode a cena novamente e confira se as animações estão corretas para cada "
 "direção. Quando tiver certeza que a movimentação está funcionando "
@@ -4510,8 +4523,9 @@ msgid "See :ref:`doc_instancing` to learn more about instancing."
 msgstr "Veja :ref:`doc_instancing` para aprender mais sobre instanciação."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
+#, fuzzy
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 "Agora adicione os seguintes nós como filhos de ``Principal``, e os nomeie "
@@ -4644,8 +4658,9 @@ msgid "Main script"
 msgstr "Script principal"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
+#, fuzzy
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 "Adicione um roteiro a ``Principal``. No começo do roteiro, nós usamos "
@@ -4688,8 +4703,9 @@ msgstr ""
 "pontuação de 1 em 1."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
+#, fuzzy
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -5332,7 +5348,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr "Exportar modelos"
@@ -5406,9 +5422,10 @@ msgstr ""
 "do seu jogo, como um `.apk` para o Android ou um `.exe` para o Windows."
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
+#, fuzzy
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 "Nas abas \"Recursos\" e \"Funcionalidades\" você pode personalizar como o "
 "jogo é exportado para cada plataforma. Podemos deixar essas configurações "
@@ -5513,8 +5530,9 @@ msgstr ""
 "comunicar com o seu dispositivo."
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
+#, fuzzy
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 "Em seguida, crie um keystore de depuração executando o seguinte comando na "
@@ -5646,9 +5664,10 @@ msgstr ""
 "seguintes arquivos:"
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
+#, fuzzy
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -5772,9 +5791,10 @@ msgid "On top of that, you can **inherit** from any scene."
 msgstr "Além disso, você pode **herdar** de qualquer cena."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
+#, fuzzy
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
@@ -5784,8 +5804,9 @@ msgstr ""
 "editor, usando apenas o código ou misturando e combinando os dois."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
+#, fuzzy
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -5942,9 +5963,10 @@ msgstr ""
 "Qualquer um destes pode vir como plugins de terceiros."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
+#, fuzzy
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -6010,8 +6032,9 @@ msgstr ""
 "plug-ins e estender o editor.**"
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
+#, fuzzy
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 "Isso leva a um sistema de interface de usuário confiável e flexível, pois "
@@ -6061,11 +6084,12 @@ msgid "Design interfaces with the Control nodes"
 msgstr "Design de interfaces com os nós de Controle"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:6
+#, fuzzy
 msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -6122,11 +6146,12 @@ msgstr ""
 "<doc_ui_game_user_interface>`."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
+#, fuzzy
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 "Use apenas os nós de controle ao projetar suas interfaces. Eles possuem "
@@ -6233,7 +6258,7 @@ msgstr "TextureRect"
 #, fuzzy
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 "**TextureRect** exibe uma textura ou imagem dentro de uma interface do "
@@ -6392,12 +6417,13 @@ msgid "TextureProgress bar, two thirds filled"
 msgstr "Barra TextureProgress, dois terços preenchidos"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:143
+#, fuzzy
 msgid ""
 "**Label** prints text to the screen. You'll find all its properties in the "
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 "O **Label** exibe texto na tela. Você encontrará todas as suas propriedades "
 "na seção Label, no Inspetor. Escreva o texto na propriedade ``Text`` e "
@@ -6462,10 +6488,11 @@ msgstr ""
 "pai."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:174
+#, fuzzy
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -6665,11 +6692,12 @@ msgid "Arrange control nodes automatically with containers"
 msgstr "Organize nós de controle automaticamente com contêineres"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:275
+#, fuzzy
 msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 "Os contêineres organizam automaticamente todos os Nós filhos de controle, "
 "incluindo outros contêineres em linhas, colunas e mais. Use-os para "
@@ -6831,9 +6859,10 @@ msgstr ""
 "Um GridContainer com 2 colunas. Ele dimensiona cada coluna automaticamente."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
+#, fuzzy
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 "O sistema de interface do usuário do Godot é complexo e tem muito mais a "
@@ -6864,8 +6893,9 @@ msgstr ""
 "dinheiro"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
+#, fuzzy
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -7310,13 +7340,15 @@ msgstr ""
 "Não há espaço entre o logotipo e os outros elementos da interface do usuário"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:219
+#, fuzzy
 msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 "Para centralizar os caracteres à direita, usaremos um ``CenterContainer``. "
 "Adicione um nó ``CenterContainer`` como filho do ``HBoxContainer``. Então no "
@@ -7358,13 +7390,15 @@ msgstr ""
 "interface do usuário"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:244
+#, fuzzy
 msgid ""
 "Now we grouped the menu options together, we can tell their container to "
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 "Agora agrupamos as opções de menu juntas, podemos dizer que o contêiner "
 "delas é expandido para ocupar o máximo de espaço vertical possível. "
@@ -7422,9 +7456,10 @@ msgstr ""
 "do jogo com barras e contadores de itens."
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
+#, fuzzy
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -8730,8 +8765,9 @@ msgid "Intro"
 msgstr "Introdução"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
+#, fuzzy
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 "Neste tutorial, você conectará um personagem a uma barra de vida e animará a "
@@ -8813,14 +8849,15 @@ msgid "To do this, we will use **signals**."
 msgstr "Para fazer isso, usaremos **sinais**."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:49
+#, fuzzy
 msgid ""
 "Signals are Godot's version of the Observer pattern. They allow us to send "
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 "Sinais são a versão Godot do padrão Observador. Eles nos permitem enviar "
@@ -8848,13 +8885,14 @@ msgstr ""
 "e` end`."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
+#, fuzzy
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 "Carregue o projeto `` start`` na Godot. No dock `` FileSystem`` clique duas "
 "vezes em LevelMockup.tscn para abri-lo. É uma maquete de um jogo de RPG onde "
@@ -8889,9 +8927,11 @@ msgid "The scene tree, with the GUI scene set to display its children"
 msgstr "A árvore de cena, com a cena GUI configurada para exibir seus filhos"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
+#, fuzzy
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 "A cena GUI encapsula toda a interface do usuário do jogo. Ela vem com um "
 "roteiro rascunhado, onde obtemos o caminho para os nós que existem dentro da "
@@ -9150,11 +9190,12 @@ msgstr ""
 "html>` _ está disponível online gratuitamente."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
+#, fuzzy
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 "Com isso em mente, vamos conectar a ``GUI`` ao ``Player``. Clique no nó "
 "``Player`` no painel Cena para selecioná-lo. Vá até o Inspetor e clique na "
@@ -9262,21 +9303,23 @@ msgid "Godot writes the callback method for you and takes you to it"
 msgstr "Godot escreve o método de callback para você e leva você até ele"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
+#, fuzzy
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 "Dentro dos parênteses após o nome da função, adicione um argumento "
 "``player_health``. Quando o jogador emite o sinal ``health_changed``, ele "
 "enviará sua ``health`` atual juntamente. Seu código deve se parecer com:"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
+#, fuzzy
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 "A engine não converte PascalCase para snake_case, por exemplos em C # "
 "estaremos usando PascalCase para nomes de métodos e camelCase para "
@@ -9293,8 +9336,9 @@ msgstr ""
 "envia seu valor de integridade"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
+#, fuzzy
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 "Dentro de `` _on_Player_health_changed`` vamos chamar uma segunda função "
@@ -9344,9 +9388,10 @@ msgid "set the ``TextureProgress``'s ``value`` to ``new_value``"
 msgstr "setar `` value`` do `` TextureProgress`` para `` new_value``"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
+#, fuzzy
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 "`` str`` é uma função interna que converte qualquer valor em texto. A "
@@ -9377,11 +9422,12 @@ msgid "Animate the loss of life with the Tween node"
 msgstr "Animar a perda de vida com o nó Tween"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:367
+#, fuzzy
 msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -9583,7 +9629,8 @@ msgstr ""
 "para a barra de vida para animar de uma forma mais bonita."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+#, fuzzy
+msgid "The animation is smooth, but the number is broken"
 msgstr "A animação é suave, mas o número está quebrado"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -9602,7 +9649,8 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr "Rode o jogo novamente para ver uma bela animação em blocos."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+#, fuzzy
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 "Ao arredondar animated\\_health, acertamos dois coelhos com uma só cajadada"
 
@@ -9706,10 +9754,11 @@ msgstr ""
 "ele e modifique-o usando uma cor com `modulate`."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:611
+#, fuzzy
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 "`` modulate`` recebe um valor `` Color`` com 4 canais: vermelho, verde, azul "
 "e alfa. Se escurecermos qualquer um dos três primeiros canais, escurecerá a "
@@ -9748,8 +9797,9 @@ msgstr ""
 "Tween`` novamente:"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
+#, fuzzy
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -9922,10 +9972,11 @@ msgstr ""
 "e nomeie a animação \"intro\" quando a caixa de diálogo aparecer."
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
+#, fuzzy
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 "Agora que temos uma animação, o editor de propriedades entra no modo "
 "\"edição de animação\". Neste modo, um ícone de chave aparece ao lado de "
@@ -10010,7 +10061,7 @@ msgstr "Nós e recursos"
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 "Até agora, :ref:`Nós <class_Node>` têm sido o tipo de dados mais importante "
@@ -10022,9 +10073,9 @@ msgstr ""
 #, fuzzy
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 "*Nodes* dão sua funcionalidade: eles desenham sprites, modelos 3D, simulam "
 "física, organizam a interface do usuário, etc. **Recursos** são **containers "
@@ -10051,7 +10102,7 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 "Quando um recurso é carregado do disco, **sempre é carregado só uma vez**. "
@@ -10064,7 +10115,7 @@ msgstr ""
 #, fuzzy
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -10110,7 +10161,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 #, fuzzy
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 "Clique com o botão direito na variável para permitir que você configure suas "
@@ -10119,10 +10170,10 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 #, fuzzy
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 "A propriedade da caminho nos diz de onde o recurso vem. Nesse caso ele vem "
 "de uma imagem PNG chamada ``robi.png``. Quando o recurso vem de um arquivo "
@@ -10214,7 +10265,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 "Essa abordagem tem várias vantagens. Como a função :ref:`PackedScene."
@@ -10264,7 +10315,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -10492,7 +10543,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 #, fuzzy
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 "CurveTables são a mesma coisa, exceto mapeado para uma matriz de valores "
@@ -10526,7 +10577,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 "Os sistemas de arquivos são outro tópico importante no desenvolvimento do "
 "motor. O sistema de arquivos gerencia como os ativos são armazenados e como "
@@ -10578,7 +10629,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 "Em geral, o sistema de arquivos Godot evita usar arquivos de metadados. A "
@@ -11179,9 +11230,9 @@ msgstr ""
 #, fuzzy
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 "Aqui você pode adicionar qualquer número de cenas ou scripts. Cada entrada "
 "na lista requer um nome, designada como a propriedade ``nome`` do nó."
@@ -11555,12 +11606,13 @@ msgstr ""
 "de cena da maneira que preferir."
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:57
+#, fuzzy
 msgid ""
 "While both editors may seem similar, there are many differences below the "
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 "Embora ambos os editores possam parecer semelhantes, há muitas diferenças "
 "por trás. Ambos permitem organizar o projeto usando o sistema de arquivos, "
@@ -11683,7 +11735,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 #, fuzzy
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -11851,12 +11903,12 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 #, fuzzy
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 "Segundo, permite a extração de uma sub-árvore de cena para torná-la uma cena "
 "própria, que responde à segunda e à terceira pergunta: mesmo que uma árvore "
@@ -11930,9 +11982,10 @@ msgstr ""
 "prefab."
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
+#, fuzzy
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -13611,10 +13664,11 @@ msgstr ""
 "podem ser negativos como em Python, para contar do final."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:489
+#, fuzzy
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -14066,8 +14120,9 @@ msgid "Remove ``case``"
 msgstr "Remova ``case``"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
+#, fuzzy
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 "Remova todos os ``break``s. Se você não quer que interrompa (``break``) por "
@@ -14159,9 +14214,10 @@ msgstr ""
 "que você possa aninhá-los."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
+#, fuzzy
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 "O comprimento do array é testado primeiro; ele tem que ter o mesmo tamanho "
 "do padrão, senão o padrão não coincide."
@@ -14191,9 +14247,10 @@ msgstr ""
 "padrão constante."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
+#, fuzzy
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 "O tamanho do dicionário é testado primeiro; ele tem que ser o mesmo tamanho "
 "do padrão, senão o padrão não coincide."
@@ -14470,11 +14527,12 @@ msgstr ""
 "(veja abaixo)."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
+#, fuzzy
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 "Um dos benefícios fundamentais de exportar variáveis membros é tê-las "
 "visíveis e editáveis no editor. Dessa forma, artistas e projetistas de jogos "
@@ -14536,8 +14594,9 @@ msgid "Exporting arrays"
 msgstr "Exportando arrays"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
+#, fuzzy
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -14601,8 +14660,9 @@ msgstr ""
 "scripts de ferramentas ou plugin, para validação do input."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
+#, fuzzy
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 "Como dito acesso *local* *não* irá iniciar o setter e getter. Aqui temos uma "
@@ -14613,9 +14673,10 @@ msgid "Tool mode"
 msgstr "Modo de Ferramenta"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
+#, fuzzy
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -14708,13 +14769,14 @@ msgid "Coroutines with yield"
 msgstr "Corrotinas com yield"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1520
+#, fuzzy
 msgid ""
 "GDScript offers support for `coroutines <https://en.wikipedia.org/wiki/"
 "Coroutine>`_ via the ``yield`` built-in function. Calling ``yield()`` will "
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 "A GDScript oferece suporte para `corrotinas <https://pt.wikipedia.org/wiki/"
 "Corotina>`_ através do comando embutido ``yield``. Chamar ``yield()`` irá "
@@ -14740,9 +14802,10 @@ msgid "Coroutines & signals"
 msgstr "Corrotinas e sinais"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
+#, fuzzy
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 "O verdadeiro poder de utilizar ``yield`` é quando combinado com sinais. "
@@ -24416,7 +24479,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "Ferramentas"
 
@@ -27371,8 +27434,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -27585,9 +27647,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -29594,7 +29656,7 @@ msgstr ":ref:`String <class_String>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
 #, fuzzy
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ":ref:`Color <class_Color>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -30332,437 +30394,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr "Jogo de tiro em primeira pessoa (FPS)"
@@ -32596,7 +32227,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -32606,7 +32237,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -48155,9 +47786,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -48207,9 +47838,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -48264,47 +47895,45 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 #, fuzzy
 msgid "Coloring the planet"
 msgstr "Configurando o projeto"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -48312,7 +47941,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -48321,7 +47950,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -48329,7 +47958,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -48339,7 +47968,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -48350,20 +47979,20 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 #, fuzzy
 msgid "Making an ocean"
 msgstr "Apagando uma cena"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -48371,13 +48000,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -48385,7 +48014,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -48394,7 +48023,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -48408,7 +48037,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -48417,7 +48046,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -48425,10 +48054,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -49397,6 +49026,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -52327,6 +51961,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -56924,11 +56984,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -57123,49 +57183,43 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 #, fuzzy
 msgid "Setting up the project"
 msgstr "Criando um novo projeto"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 #, fuzzy
 msgid "There are a few prerequisites you'll need:"
 msgstr "Existem algumas diferenças:"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-#, fuzzy
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-"Dê um Fork `Repositório do  Godot<https://github.com/godotengine/godot>`_"
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -57173,29 +57227,30 @@ msgid ""
 msgstr ""
 "Dê um Fork `Repositório do  Godot<https://github.com/godotengine/godot>`_"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -57203,132 +57258,128 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 #, fuzzy
 msgid "Creating a simple plugin"
 msgstr "Criando um script C#"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -57336,56 +57387,56 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 #, fuzzy
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr "Comece declarando as variáveis membro que este objeto irá precisar:"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -57396,22 +57447,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -57420,7 +57471,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -57428,11 +57479,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -57441,42 +57492,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -57486,7 +57544,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -57495,7 +57553,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -57503,58 +57561,256 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+#, fuzzy
+msgid "Adding properties"
+msgstr "Propriedades do Node"
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -59651,7 +59907,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -59659,18 +59915,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -59678,23 +59934,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -59702,35 +59958,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -59739,103 +59995,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -59843,20 +60099,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -59895,11 +60151,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -59909,24 +60177,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -59935,7 +60203,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -59943,18 +60211,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -59964,7 +60232,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -59973,37 +60241,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -60011,63 +60279,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -60075,13 +60343,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -60089,7 +60357,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -60097,25 +60365,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -60123,30 +60391,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -60154,7 +60422,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -60163,25 +60431,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -60192,46 +60460,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -60240,68 +60508,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -60309,7 +60577,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -60318,11 +60586,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -60330,114 +60598,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -60504,37 +60772,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -60542,61 +60810,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -60616,18 +60884,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -60635,11 +60903,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -60647,37 +60915,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -60738,27 +61006,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -60766,24 +61034,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -60791,29 +61046,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -60821,35 +61076,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -60857,40 +61112,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -60898,131 +61153,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -61042,29 +61297,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -61075,17 +61330,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "Rodar"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -61195,6 +61450,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -61279,61 +61538,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -61342,13 +61601,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -61357,11 +61616,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -61369,14 +61628,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -61384,14 +61643,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -61400,14 +61659,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -61417,7 +61676,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -61426,7 +61685,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -61435,7 +61694,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -61466,7 +61725,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -61476,7 +61735,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -61484,14 +61743,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -61499,21 +61758,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -61522,7 +61781,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -61532,7 +61791,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
@@ -68203,6 +68462,13 @@ msgstr ""
 "'Zeef Godot Engine: A curated directory of resources by Andre Schmitz "
 "<https://godot-engine.zeef.com/andre.antonio.schmitz>'_"
 
+#, fuzzy
+#~ msgid ""
+#~ "a copy of the `godot_headers repository <https://github.com/"
+#~ "GodotNativeTools/godot_headers>`_,"
+#~ msgstr ""
+#~ "Dê um Fork `Repositório do  Godot<https://github.com/godotengine/godot>`_"
+
 #, fuzzy
 #~ msgid ""
 #~ "NOTE: The result of these operations depends on the operands types. If "
diff --git a/weblate/pt_PT.po b/weblate/pt_PT.po
index 8cf81357c2..72f690a2eb 100644
--- a/weblate/pt_PT.po
+++ b/weblate/pt_PT.po
@@ -13,7 +13,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-12-03 19:26+0000\n"
 "Last-Translator: ssantos <ssantos@web.de>\n"
 "Language-Team: Portuguese (Portugal) <https://hosted.weblate.org/projects/"
@@ -80,13 +80,14 @@ msgstr ""
 "procura na documentação, ajude-nos a melhorar, contactando-nos!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Envie seu problema ou \"pull request\" no `repositório GitHub <https://"
 "github.com/godotengine/godot-docs/issues>`_, ajude-nos a `traduzir a "
@@ -158,7 +159,6 @@ msgstr "Sobre Nós"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -177,6 +177,7 @@ msgstr "Sobre Nós"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -382,10 +383,11 @@ msgstr ""
 "desenvolvimento de módulos em C++, ou plugins para o editor."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1636,7 +1638,8 @@ msgid "It can be extended (to have more functions)."
 msgstr "Pode ser estendido (ter mais funções)."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+#, fuzzy
+msgid "It can be added to another node as a child."
 msgstr "Pode ser adicionado a outros nós como filho."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -2256,13 +2259,14 @@ msgstr ""
 "(seja por código ou diretamente pelo editor) para as relações de posse."
 
 #: ../../docs/getting_started/step_by_step/instancing_continued.rst:43
+#, fuzzy
 msgid ""
 "A lot of time spent in programming games (or software in general) is on "
 "designing an architecture and fitting game components to that architecture. "
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 "Muito do tempo gasto em programação de jogos (ou de softwares em geral) é "
@@ -2372,16 +2376,18 @@ msgstr ""
 "a habilidade de adicionar linguagens de roteirização extras dinamicamente!"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
+#, fuzzy
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 "Isso é ótimo, principalmente por causa da enorme flexibilidade oferecida, "
 "mas também dificulta nosso trabalho de dar suporte a linguagens."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
+#, fuzzy
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2700,9 +2706,10 @@ msgstr ""
 "relevantes."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
+#, fuzzy
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 "Na GDScript, o ficheiro em si representa a classe, então o campo de nome da "
 "classe não é editável."
@@ -2733,9 +2740,10 @@ msgstr ""
 "Script no Inspetor:"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
+#, fuzzy
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 "Para editar o roteiro, selecione um desses botões, ambos destacados na "
@@ -2836,11 +2844,12 @@ msgstr ""
 "método a ser disparado."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:205
+#, fuzzy
 msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 "A seção superior esquerda mostra uma lista com nós da sua cena, com o nome "
 "do nó emissor destacado em vermelho. Selecione o nó \"Painel\" aqui. Quando "
@@ -2860,9 +2869,10 @@ msgstr ""
 "para você antes de configurar a conexão."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
+#, fuzzy
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 "E isso conclui o guia sobre como usar a interface visual. Entretanto, isso é "
@@ -3328,6 +3338,7 @@ msgstr "Apenas GDScript pode criar variáveis globais para cada script nomeado."
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Sinais"
@@ -3983,10 +3994,11 @@ msgstr ""
 "uma boa hora para descobrir o tamanho da janela do jogo:"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:198
+#, fuzzy
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 "Agora podemos usar a função ``_process()`` para definir o que o jogador "
 "fará. ``_process()`` é chamada a cada quadro, então usaremos isso para "
@@ -4166,10 +4178,11 @@ msgstr ""
 "acima:"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:372
+#, fuzzy
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 "Rode a cena novamente e confira se as animações estão corretas para cada "
 "direção. Quando tiver certeza que a movimentação está funcionando "
@@ -4457,8 +4470,9 @@ msgid "See :ref:`doc_instancing` to learn more about instancing."
 msgstr "Veja :ref:`doc_instancing` para aprender mais sobre instanciação."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
+#, fuzzy
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 "Agora adicione os seguintes nós como filhos de ``Principal``, e os nomeie "
@@ -4591,8 +4605,9 @@ msgid "Main script"
 msgstr "Script principal"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
+#, fuzzy
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 "Adicione um roteiro a ``Principal``. No começo do roteiro, nós usamos "
@@ -4635,8 +4650,9 @@ msgstr ""
 "pontuação de 1 em 1."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
+#, fuzzy
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -5278,7 +5294,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr "Exportar modelos"
@@ -5352,9 +5368,10 @@ msgstr ""
 "do seu jogo, como um `.apk` para o Android ou um `.exe` para o Windows."
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
+#, fuzzy
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 "Nas abas \"Recursos\" e \"Funcionalidades\" você pode personalizar como o "
 "jogo é exportado para cada plataforma. Podemos deixar essas configurações "
@@ -5458,8 +5475,9 @@ msgstr ""
 "comunicar com o seu dispositivo."
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
+#, fuzzy
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 "Em seguida, crie um keystore de depuração executando o seguinte comando na "
@@ -5591,9 +5609,10 @@ msgstr ""
 "seguintes ficheiros:"
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
+#, fuzzy
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -5717,9 +5736,10 @@ msgid "On top of that, you can **inherit** from any scene."
 msgstr "Além disso, você pode **herdar** de qualquer cena."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
+#, fuzzy
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
@@ -5729,8 +5749,9 @@ msgstr ""
 "editor, usando apenas o código ou misturando e combinando os dois."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
+#, fuzzy
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -5887,9 +5908,10 @@ msgstr ""
 "Qualquer um destes pode vir como plugins de terceiros."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
+#, fuzzy
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -5955,8 +5977,9 @@ msgstr ""
 "plug-ins e estender o editor.**"
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
+#, fuzzy
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 "Isso leva a um sistema de interface de usuário confiável e flexível, pois "
@@ -6006,11 +6029,12 @@ msgid "Design interfaces with the Control nodes"
 msgstr "Design de interfaces com os nós de Controle"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:6
+#, fuzzy
 msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -6067,11 +6091,12 @@ msgstr ""
 "<doc_ui_game_user_interface>`."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
+#, fuzzy
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 "Use apenas os nós de controle ao projetar suas interfaces. Eles possuem "
@@ -6178,7 +6203,7 @@ msgstr "TextureRect"
 #, fuzzy
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 "**TextureRect** exibe uma textura ou imagem dentro de uma interface do "
@@ -6337,12 +6362,13 @@ msgid "TextureProgress bar, two thirds filled"
 msgstr "Barra TextureProgress, dois terços preenchidos"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:143
+#, fuzzy
 msgid ""
 "**Label** prints text to the screen. You'll find all its properties in the "
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 "O **Label** exibe texto na tela. Você encontrará todas as suas propriedades "
 "na seção Label, no Inspetor. Escreva o texto na propriedade ``Text`` e "
@@ -6407,10 +6433,11 @@ msgstr ""
 "pai."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:174
+#, fuzzy
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -6610,11 +6637,12 @@ msgid "Arrange control nodes automatically with containers"
 msgstr "Organize nós de controle automaticamente com contêineres"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:275
+#, fuzzy
 msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 "Os contêineres organizam automaticamente todos os Nós filhos de controle, "
 "incluindo outros contêineres em linhas, colunas e mais. Use-os para "
@@ -6776,9 +6804,10 @@ msgstr ""
 "Um GridContainer com 2 colunas. Ele dimensiona cada coluna automaticamente."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
+#, fuzzy
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 "O sistema de interface do usuário do Godot é complexo e tem muito mais a "
@@ -6809,8 +6838,9 @@ msgstr ""
 "dinheiro"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
+#, fuzzy
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -7255,13 +7285,15 @@ msgstr ""
 "Não há espaço entre o logotipo e os outros elementos da interface do usuário"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:219
+#, fuzzy
 msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 "Para centralizar os caracteres à direita, usaremos um ``CenterContainer``. "
 "Adicione um nó ``CenterContainer`` como filho do ``HBoxContainer``. Então no "
@@ -7303,13 +7335,15 @@ msgstr ""
 "interface do usuário"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:244
+#, fuzzy
 msgid ""
 "Now we grouped the menu options together, we can tell their container to "
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 "Agora agrupamos as opções de menu juntas, podemos dizer que o contêiner "
 "delas é expandido para ocupar o máximo de espaço vertical possível. "
@@ -7367,9 +7401,10 @@ msgstr ""
 "do usuário do jogo com barras e contadores de itens."
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
+#, fuzzy
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -8668,8 +8703,9 @@ msgid "Intro"
 msgstr "Introdução"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
+#, fuzzy
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 "Neste tutorial, você conectará um personagem a uma barra de vida e animará a "
@@ -8751,14 +8787,15 @@ msgid "To do this, we will use **signals**."
 msgstr "Para fazer isso, usaremos **sinais**."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:49
+#, fuzzy
 msgid ""
 "Signals are Godot's version of the Observer pattern. They allow us to send "
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 "Sinais são a versão Godot do padrão Observador. Eles nos permitem enviar "
@@ -8786,13 +8823,14 @@ msgstr ""
 "e` end`."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
+#, fuzzy
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 "Carregue o projeto `` start`` na Godot. No dock `` FileSystem`` clique duas "
 "vezes em LevelMockup.tscn para abri-lo. É uma maquete de um jogo de RPG onde "
@@ -8827,9 +8865,11 @@ msgid "The scene tree, with the GUI scene set to display its children"
 msgstr "A árvore de cena, com a cena GUI configurada para exibir seus filhos"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
+#, fuzzy
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 "A cena GUI encapsula toda a interface do usuário do jogo. Ela vem com um "
 "roteiro rascunhado, onde obtemos o caminho para os nós que existem dentro da "
@@ -9088,11 +9128,12 @@ msgstr ""
 "html>` _ está disponível online gratuitamente."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
+#, fuzzy
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 "Com isso em mente, vamos conectar a ``GUI`` ao ``Player``. Clique no nó "
 "``Player`` no painel Cena para selecioná-lo. Vá até o Inspetor e clique na "
@@ -9200,21 +9241,23 @@ msgid "Godot writes the callback method for you and takes you to it"
 msgstr "Godot escreve o método de callback para você e leva você até ele"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
+#, fuzzy
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 "Dentro dos parênteses após o nome da função, adicione um argumento "
 "``player_health``. Quando o jogador emite o sinal ``health_changed``, ele "
 "enviará sua ``health`` atual juntamente. Seu código deve se parecer com:"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
+#, fuzzy
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 "A engine não converte PascalCase para snake_case, por exemplos em C # "
 "estaremos usando PascalCase para nomes de métodos e camelCase para "
@@ -9231,8 +9274,9 @@ msgstr ""
 "envia seu valor de integridade"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
+#, fuzzy
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 "Dentro de `` _on_Player_health_changed`` vamos chamar uma segunda função "
@@ -9282,9 +9326,10 @@ msgid "set the ``TextureProgress``'s ``value`` to ``new_value``"
 msgstr "setar `` value`` do `` TextureProgress`` para `` new_value``"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
+#, fuzzy
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 "`` str`` é uma função interna que converte qualquer valor em texto. A "
@@ -9315,11 +9360,12 @@ msgid "Animate the loss of life with the Tween node"
 msgstr "Animar a perda de vida com o nó Tween"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:367
+#, fuzzy
 msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -9521,7 +9567,8 @@ msgstr ""
 "para a barra de vida para animar de uma forma mais bonita."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+#, fuzzy
+msgid "The animation is smooth, but the number is broken"
 msgstr "A animação é suave, mas o número está quebrado"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -9540,7 +9587,8 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr "Rode o jogo novamente para ver uma bela animação em blocos."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+#, fuzzy
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 "Ao arredondar animated\\_health, acertamos dois coelhos com uma só cajadada"
 
@@ -9644,10 +9692,11 @@ msgstr ""
 "ele e modifique-o usando uma cor com `modulate`."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:611
+#, fuzzy
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 "`` modulate`` recebe um valor `` Color`` com 4 canais: vermelho, verde, azul "
 "e alfa. Se escurecermos qualquer um dos três primeiros canais, escurecerá a "
@@ -9686,8 +9735,9 @@ msgstr ""
 "Tween`` novamente:"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
+#, fuzzy
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -9860,10 +9910,11 @@ msgstr ""
 "e nomeie a animação \"intro\" quando a caixa de diálogo aparecer."
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
+#, fuzzy
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 "Agora que temos uma animação, o editor de propriedades entra no modo "
 "\"edição de animação\". Neste modo, um ícone de chave aparece ao lado de "
@@ -9948,7 +9999,7 @@ msgstr "Nós e recursos"
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 "Até agora, :ref:`Nós <class_Node>` têm sido o tipo de dados mais importante "
@@ -9959,9 +10010,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -9984,7 +10035,7 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 "Quando um recurso é carregado do disco, **sempre é carregado só uma vez**. "
@@ -9997,7 +10048,7 @@ msgstr ""
 #, fuzzy
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -10039,7 +10090,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 #, fuzzy
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 "Clique com o botão direito na variável para permitir que você configure suas "
@@ -10047,10 +10098,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -10124,7 +10175,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 "Essa abordagem tem várias vantagens. Como a função :ref:`PackedScene."
@@ -10168,7 +10219,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -10315,7 +10366,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -10341,11 +10392,12 @@ msgid "File system"
 msgstr "Sistema de ficheiros"
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:9
+#, fuzzy
 msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 "Os sistemas de ficheiros são outro tópico importante no desenvolvimento do "
 "motor. O sistema de ficheiros gerencia como os ativos são armazenados e como "
@@ -10392,10 +10444,11 @@ msgstr ""
 "é empacotado junto com as texturas de fonte."
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:30
+#, fuzzy
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 "Em geral, o sistema de ficheiros Godot evita usar ficheiros de metadados. A "
@@ -10995,9 +11048,9 @@ msgstr ""
 #, fuzzy
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 "Aqui você pode adicionar qualquer número de cenas ou scripts. Cada entrada "
 "na lista requer um nome, designada como a propriedade ``nome`` do nó."
@@ -11370,12 +11423,13 @@ msgstr ""
 "de cena da maneira que preferir."
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:57
+#, fuzzy
 msgid ""
 "While both editors may seem similar, there are many differences below the "
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 "Embora ambos os editores possam parecer semelhantes, há muitas diferenças "
 "por trás. Ambos permitem organizar o projeto usando o sistema de ficheiros, "
@@ -11496,8 +11550,9 @@ msgstr ""
 "eles."
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
+#, fuzzy
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -11665,12 +11720,12 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 #, fuzzy
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 "Segundo, permite a extração de uma sub-árvore de cena para torná-la uma cena "
 "própria, que responde à segunda e à terceira pergunta: mesmo que uma árvore "
@@ -11744,9 +11799,10 @@ msgstr ""
 "prefab."
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
+#, fuzzy
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -13425,10 +13481,11 @@ msgstr ""
 "podem ser negativos como em Python, para contar do final."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:489
+#, fuzzy
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -13880,8 +13937,9 @@ msgid "Remove ``case``"
 msgstr "Remova ``case``"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
+#, fuzzy
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 "Remova todos os ``break``s. Se você não quer que interrompa (``break``) por "
@@ -13973,9 +14031,10 @@ msgstr ""
 "que você possa aninhá-los."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
+#, fuzzy
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 "O comprimento do array é testado primeiro; ele tem que ter o mesmo tamanho "
 "do padrão, senão o padrão não coincide."
@@ -14005,9 +14064,10 @@ msgstr ""
 "padrão constante."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
+#, fuzzy
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 "O tamanho do dicionário é testado primeiro; ele tem que ser o mesmo tamanho "
 "do padrão, senão o padrão não coincide."
@@ -14284,11 +14344,12 @@ msgstr ""
 "(veja abaixo)."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
+#, fuzzy
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 "Um dos benefícios fundamentais de exportar variáveis membros é tê-las "
 "visíveis e editáveis no editor. Dessa forma, artistas e projetistas de jogos "
@@ -14350,8 +14411,9 @@ msgid "Exporting arrays"
 msgstr "Exportando arrays"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
+#, fuzzy
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -14415,8 +14477,9 @@ msgstr ""
 "scripts de ferramentas ou plugin, para validação do input."
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
+#, fuzzy
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 "Como dito acesso *local* *não* irá iniciar o setter e getter. Aqui temos uma "
@@ -14427,9 +14490,10 @@ msgid "Tool mode"
 msgstr "Modo de Ferramenta"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
+#, fuzzy
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -14522,13 +14586,14 @@ msgid "Coroutines with yield"
 msgstr "Corrotinas com yield"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1520
+#, fuzzy
 msgid ""
 "GDScript offers support for `coroutines <https://en.wikipedia.org/wiki/"
 "Coroutine>`_ via the ``yield`` built-in function. Calling ``yield()`` will "
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 "A GDScript oferece suporte para `corrotinas <https://pt.wikipedia.org/wiki/"
 "Corotina>`_ através do comando embutido ``yield``. Chamar ``yield()`` irá "
@@ -14554,9 +14619,10 @@ msgid "Coroutines & signals"
 msgstr "Corrotinas e sinais"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
+#, fuzzy
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 "O verdadeiro poder de utilizar ``yield`` é quando combinado com sinais. "
@@ -24205,7 +24271,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "Ferramentas"
 
@@ -27160,8 +27226,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -27374,9 +27439,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -29383,7 +29448,7 @@ msgstr ":ref:`String <class_String>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
 #, fuzzy
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ":ref:`Color <class_Color>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -30121,437 +30186,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr "Jogo de tiro em primeira pessoa (FPS)"
@@ -32385,7 +32019,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -32395,7 +32029,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -47944,9 +47578,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -47996,9 +47630,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -48053,47 +47687,45 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 #, fuzzy
 msgid "Coloring the planet"
 msgstr "Configurando o projeto"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -48101,7 +47733,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -48110,7 +47742,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -48118,7 +47750,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -48128,7 +47760,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -48139,20 +47771,20 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 #, fuzzy
 msgid "Making an ocean"
 msgstr "Apagando uma cena"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -48160,13 +47792,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -48174,7 +47806,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -48183,7 +47815,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -48197,7 +47829,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -48206,7 +47838,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -48214,10 +47846,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -49186,6 +48818,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -52116,6 +51753,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -56713,11 +56776,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -56912,49 +56975,43 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 #, fuzzy
 msgid "Setting up the project"
 msgstr "Criando um novo projeto"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 #, fuzzy
 msgid "There are a few prerequisites you'll need:"
 msgstr "Existem algumas diferenças:"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-#, fuzzy
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-"Dê um Fork `Repositório do  Godot<https://github.com/godotengine/godot>`_"
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -56962,29 +57019,30 @@ msgid ""
 msgstr ""
 "Dê um Fork `Repositório do  Godot<https://github.com/godotengine/godot>`_"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -56992,132 +57050,128 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 #, fuzzy
 msgid "Creating a simple plugin"
 msgstr "Criando um script C#"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -57125,56 +57179,56 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 #, fuzzy
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr "Comece declarando as variáveis membro que este objeto irá precisar:"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -57185,22 +57239,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -57209,7 +57263,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -57217,11 +57271,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -57230,42 +57284,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -57275,7 +57336,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -57284,7 +57345,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -57292,58 +57353,256 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+#, fuzzy
+msgid "Adding properties"
+msgstr "Propriedades do Node"
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -59440,7 +59699,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -59448,18 +59707,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -59467,23 +59726,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -59491,35 +59750,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -59528,103 +59787,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -59632,20 +59891,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -59684,11 +59943,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -59698,24 +59969,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -59724,7 +59995,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -59732,18 +60003,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -59753,7 +60024,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -59762,37 +60033,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -59800,63 +60071,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -59864,13 +60135,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -59878,7 +60149,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -59886,25 +60157,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -59912,30 +60183,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -59943,7 +60214,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -59952,25 +60223,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -59981,46 +60252,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -60029,68 +60300,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -60098,7 +60369,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -60107,11 +60378,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -60119,114 +60390,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -60293,37 +60564,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -60331,61 +60602,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -60405,18 +60676,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -60424,11 +60695,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -60436,37 +60707,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -60527,27 +60798,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -60555,24 +60826,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -60580,29 +60838,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -60610,35 +60868,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -60646,40 +60904,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -60687,131 +60945,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -60831,29 +61089,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -60864,17 +61122,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "Executar"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -60984,6 +61242,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -61068,61 +61330,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -61131,13 +61393,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -61146,11 +61408,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -61158,14 +61420,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -61173,14 +61435,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -61189,14 +61451,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -61206,7 +61468,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -61215,7 +61477,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -61224,7 +61486,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -61255,7 +61517,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -61265,7 +61527,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -61273,14 +61535,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -61288,21 +61550,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -61311,7 +61573,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -61321,7 +61583,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
@@ -67990,6 +68252,13 @@ msgstr ""
 "'Zeef Godot Engine: A curated directory of resources by Andre Schmitz "
 "<https://godot-engine.zeef.com/andre.antonio.schmitz>'_"
 
+#, fuzzy
+#~ msgid ""
+#~ "a copy of the `godot_headers repository <https://github.com/"
+#~ "GodotNativeTools/godot_headers>`_,"
+#~ msgstr ""
+#~ "Dê um Fork `Repositório do  Godot<https://github.com/godotengine/godot>`_"
+
 #~ msgid "Mac OS X"
 #~ msgstr "Mac OS X"
 
diff --git a/weblate/ro.po b/weblate/ro.po
index db2b837382..1724fd57aa 100644
--- a/weblate/ro.po
+++ b/weblate/ro.po
@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-08-05 00:52+0000\n"
 "Last-Translator: Grigore Antoniuc <grisa181@gmail.com>\n"
 "Language-Team: Romanian <https://hosted.weblate.org/projects/godot-engine/"
@@ -76,13 +76,14 @@ msgstr ""
 "în documentație, ajută-ne să facem documentația mai bună anunțându-ne!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Trimiteți o problemă sau un pull request în `repository-ul GitHub <https://"
 "github.com/godotengine/godot-docs/issues>`_, ajută-ne `să traducem "
@@ -155,7 +156,6 @@ msgstr "Despre"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -174,6 +174,7 @@ msgstr "Despre"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -376,10 +377,11 @@ msgstr ""
 "engine-ului,dezvoltarea modulelor C++ sau plugin-urilor pentru editor."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1385,7 +1387,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1852,7 +1854,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1927,13 +1929,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2177,8 +2179,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2202,7 +2204,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2276,7 +2278,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2290,7 +2292,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2630,6 +2632,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Semnale"
@@ -3101,7 +3104,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3227,7 +3230,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3437,7 +3440,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3535,7 +3538,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3563,7 +3566,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -4061,7 +4064,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4118,8 +4121,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4195,7 +4198,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4292,7 +4295,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4378,14 +4381,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4494,7 +4497,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4540,7 +4543,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4580,7 +4583,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4621,9 +4624,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4711,7 +4714,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4828,7 +4831,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4876,7 +4879,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -5018,7 +5021,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5126,7 +5129,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5150,7 +5153,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5477,9 +5480,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5509,8 +5513,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5550,8 +5555,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6453,7 +6458,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6522,9 +6527,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6541,12 +6546,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6569,8 +6574,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6746,10 +6752,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6828,16 +6834,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6848,7 +6854,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6890,7 +6896,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6917,7 +6923,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -7066,7 +7072,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7081,7 +7087,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7159,7 +7165,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7186,7 +7192,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7323,9 +7329,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7394,16 +7400,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7420,14 +7426,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7458,16 +7464,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7529,7 +7535,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7559,7 +7565,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7705,7 +7711,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7735,7 +7741,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7767,7 +7773,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8202,9 +8208,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8513,7 +8519,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8593,7 +8599,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8710,12 +8716,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8767,7 +8773,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10204,7 +10210,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10584,7 +10590,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10663,7 +10669,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10689,7 +10695,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10900,9 +10906,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10947,7 +10953,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10993,7 +10999,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -11004,7 +11010,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11075,7 +11081,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11095,7 +11101,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19479,7 +19485,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "Unelte"
 
@@ -22414,8 +22420,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22628,9 +22633,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24615,7 +24620,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25346,437 +25351,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27542,7 +27116,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27552,7 +27126,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42849,9 +42423,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42901,9 +42475,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42957,46 +42531,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -43004,7 +42576,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -43013,7 +42585,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -43021,7 +42593,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -43031,7 +42603,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -43042,19 +42614,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -43062,13 +42634,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43076,7 +42648,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43085,7 +42657,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43099,7 +42671,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43108,7 +42680,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43116,10 +42688,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44084,6 +43656,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46999,6 +46576,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51544,11 +51547,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51742,73 +51745,70 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51816,131 +51816,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51948,55 +51944,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -52007,22 +52003,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -52031,7 +52027,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -52039,11 +52035,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -52052,42 +52048,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52097,7 +52100,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52106,7 +52109,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52114,58 +52117,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54256,7 +54456,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54264,18 +54464,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54283,23 +54483,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54307,35 +54507,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54344,103 +54544,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54448,20 +54648,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54500,11 +54700,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54514,24 +54726,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54540,7 +54752,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54548,18 +54760,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54569,7 +54781,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54578,37 +54790,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54616,63 +54828,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54680,13 +54892,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54694,7 +54906,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54702,25 +54914,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54728,30 +54940,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54759,7 +54971,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54768,25 +54980,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54797,46 +55009,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54845,68 +55057,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54914,7 +55126,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54923,11 +55135,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54935,114 +55147,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55109,37 +55321,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55147,61 +55359,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55221,18 +55433,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55240,11 +55452,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55252,37 +55464,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55343,27 +55555,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55371,24 +55583,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55396,29 +55595,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55426,35 +55625,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55462,40 +55661,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55503,131 +55702,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55647,29 +55846,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55680,17 +55879,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "Execută"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55800,6 +55999,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55884,61 +56087,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55947,13 +56150,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55962,11 +56165,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55974,14 +56177,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55989,14 +56192,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -56005,14 +56208,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -56022,7 +56225,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -56031,7 +56234,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -56040,7 +56243,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56071,7 +56274,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56081,7 +56284,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56089,14 +56292,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56104,21 +56307,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56127,7 +56330,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56137,7 +56340,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/ru.po b/weblate/ru.po
index ff597f9ddc..1d9e408508 100644
--- a/weblate/ru.po
+++ b/weblate/ru.po
@@ -62,7 +62,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-12-03 18:32+0000\n"
 "Last-Translator: Александр <ol-vin@mail.ru>\n"
 "Language-Team: Russian <https://hosted.weblate.org/projects/godot-engine/"
@@ -128,13 +128,14 @@ msgstr ""
 "ее лучше, рассказав об этом!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Опубликуйте вопрос или получите запрос на `GitHub репозитории <https://"
 "github.com/godotengine/godot-docs/issues>`_, помогите нам `перевести "
@@ -206,7 +207,6 @@ msgstr "О движке"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -225,6 +225,7 @@ msgstr "О движке"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -421,10 +422,11 @@ msgstr ""
 "компилировать движок, разрабатывать модули на C++ или плагины для редактора."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1682,7 +1684,8 @@ msgid "It can be extended (to have more functions)."
 msgstr "Он может быть расширен (чтобы иметь больше функций)."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+#, fuzzy
+msgid "It can be added to another node as a child."
 msgstr "Он может быть добавлен к другому ноду в качестве дочернего."
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -2304,13 +2307,14 @@ msgstr ""
 "принадлежности одних компонентов к другим."
 
 #: ../../docs/getting_started/step_by_step/instancing_continued.rst:43
+#, fuzzy
 msgid ""
 "A lot of time spent in programming games (or software in general) is on "
 "designing an architecture and fitting game components to that architecture. "
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 "Много времени тратится на программирование игр (или программного обеспечения "
@@ -2419,16 +2423,18 @@ msgstr ""
 "скриптовые языки!"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
+#, fuzzy
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 "Это здорово, из-за большей гибкости, но также это затрудняет нашу работу по "
 "поддержке различных языков."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
+#, fuzzy
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2749,9 +2755,10 @@ msgstr ""
 "можете указать язык сценария, имя класса и другие параметры."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
+#, fuzzy
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 "В GDScript сам файл представляет собой класс, поэтому поле имени класса не "
 "редактируется."
@@ -2782,9 +2789,10 @@ msgstr ""
 "свойстве сценария в \"Инспекторе\":"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
+#, fuzzy
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 "Чтобы отредактировать сценарий, нажмите одну из кнопок, которые отмечены в "
@@ -2885,11 +2893,12 @@ msgstr ""
 "здесь как NodePath), и имя метода для запуска."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:205
+#, fuzzy
 msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 "В левом верхнем разделе отображается список узлов вашей сцены, где имя "
 "излучающего узла выделено красным цветом. Выберите узел \"Panel\". Когда вы "
@@ -2909,9 +2918,10 @@ msgstr ""
 "генерировать эту функцию перед настройкой соединения."
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
+#, fuzzy
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 "На этом завершим наше обучение по использованию визуального интерфейса. Всё "
@@ -3372,6 +3382,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Сигналы"
@@ -4022,10 +4033,11 @@ msgstr ""
 "является хорошим моментом для определения размера игрового окна:"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:198
+#, fuzzy
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 "Сейчас мы можем использовать функцию ``_process()`` для определения того, "
 "что игрок будет делать. ``_process()`` вызывается каждый кадр, поэтому мы "
@@ -4206,10 +4218,11 @@ msgstr ""
 "присваиванием выше:"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:372
+#, fuzzy
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 "Снова запустите сцену и убедитесь, что анимация правильная для каждого из "
 "направлений. Когда вы будете уверены, что движение работает правильно, "
@@ -4488,8 +4501,9 @@ msgstr ""
 "Посмотрите :ref:`doc_instancing`, чтобы узнать больше об инстанцировании."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
+#, fuzzy
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 "Теперь добавьте следующие узлы в виде дочерних элементов ``Main`` и назовите "
@@ -4619,8 +4633,9 @@ msgid "Main script"
 msgstr "Главный скрипт"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
+#, fuzzy
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 "Добавьте скрипт к узлу ``Main``. В верхней части скрипта мы используем "
@@ -4659,8 +4674,9 @@ msgstr ""
 "запустит другие два таймера. ``ScoreTimer`` будет увеличивать счет на 1."
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
+#, fuzzy
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -5294,7 +5310,7 @@ msgstr "Вот полный скрипт для игрока, с коммент
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr "Экспорт шаблонов"
@@ -5367,9 +5383,10 @@ msgstr ""
 "проекта, на подобию `.apk`на Android или `.exe`на Windows."
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
+#, fuzzy
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 "На вкладках \"Ресурсы\" и \"Особенности\" вы можете настроить экспорт игры "
 "для каждой платформы. Эти настройки пока оставим."
@@ -5474,8 +5491,9 @@ msgstr ""
 "взаимодействия с вашим устройством."
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
+#, fuzzy
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 "Далее создайте хранилище ключей для отладки, выполнив следующую команду в "
@@ -5605,9 +5623,10 @@ msgstr ""
 "файлы:"
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
+#, fuzzy
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -5727,9 +5746,10 @@ msgid "On top of that, you can **inherit** from any scene."
 msgstr "Более того, вы можете **наследовать** от любой сцены."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
+#, fuzzy
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
@@ -5739,8 +5759,9 @@ msgstr ""
 "только код или и то, и другое одновременно."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
+#, fuzzy
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -5901,9 +5922,10 @@ msgstr ""
 "плагин."
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
+#, fuzzy
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -5968,8 +5990,9 @@ msgstr ""
 "игр или **создавать плагины и расширять редактор.**"
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
+#, fuzzy
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 "Это приводит к созданию надежной и гибкой системы пользовательского "
@@ -6024,7 +6047,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -6082,11 +6105,12 @@ msgstr ""
 "игры в Godot <doc_ui_game_user_interface>`."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
+#, fuzzy
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 "Используйте исключительно узлы контроля, когда Вы создаете дизайн "
@@ -6194,7 +6218,7 @@ msgstr "TextureRect"
 #, fuzzy
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 "**TextureRect** отображает текстуру или изображение внутри пользовательского "
@@ -6355,12 +6379,13 @@ msgid "TextureProgress bar, two thirds filled"
 msgstr "TextureProgress шкала, две трети заполнены"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:143
+#, fuzzy
 msgid ""
 "**Label** prints text to the screen. You'll find all its properties in the "
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 "**Label** выводит текст на экран. Его свойства находятся в разделе Label, в "
 "инспекторе. Напишите текст в поле ``Text``, и проверьте Autowrap если вы не "
@@ -6419,10 +6444,11 @@ msgstr ""
 "разместить и изменить размер элемента внутри его родителя."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:174
+#, fuzzy
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -6618,11 +6644,12 @@ msgid "Arrange control nodes automatically with containers"
 msgstr "Автоматическая организация управляющих узлов с контейнерами"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:275
+#, fuzzy
 msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 "Контейнеры автоматически организовывают всех потомков управляющих узлов, "
 "заключая другие контейнеры в строки, столбцы и прочее. Используйте их, чтобы "
@@ -6784,9 +6811,10 @@ msgid "A GridContainer with 2 columns. It sizes each column automatically."
 msgstr "GridContainer с 2 колонками. Он вычисляет их размер автоматически."
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
+#, fuzzy
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 "Система UI в Godot сложна и включает гораздо больше, чем описано здесь. Для "
@@ -6819,7 +6847,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 #, fuzzy
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -7272,9 +7300,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 "Чтобы центрировать картинку справа, мы будем использовать "
 "``CenterContainer``.  Добавьте узел ``CenterContainer`` в качестве дочернего "
@@ -7324,8 +7353,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 "Теперь мы сгруппировали варианты меню вместе, мы можем сказать их "
 "контейнерам расшириться как можно больше вертикально. Выберите узел "
@@ -7383,8 +7413,8 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 #, fuzzy
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -8714,8 +8744,9 @@ msgid "Intro"
 msgstr "Введение"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
+#, fuzzy
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 "В этом уроке вы присоедините шкалу жизни к персонажу и сделаете анимацию "
@@ -8797,14 +8828,15 @@ msgid "To do this, we will use **signals**."
 msgstr "Для этого мы будем использовать **сигналы**."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:49
+#, fuzzy
 msgid ""
 "Signals are Godot's version of the Observer pattern. They allow us to send "
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 "Сигналы — это своя версия шаблона Observer в Godot. Они позволяют нам "
@@ -8832,13 +8864,14 @@ msgstr ""
 "`end`."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
+#, fuzzy
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 "Загрузите проект ``start`` в Godot. В ``Файловой системе`` дважды щелкните "
 "на LevelMockup.tscn, чтобы открыть её. Это макет RPG игры, где 2 персонажа "
@@ -8874,9 +8907,11 @@ msgid "The scene tree, with the GUI scene set to display its children"
 msgstr "Дерево сцены, с GUI которая отображает своих детей"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
+#, fuzzy
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 "Сцена GUI инкапсулирует весь интерфейс игры. Он идет с каркасом скрипта, где "
 "мы получаем путь к узлам, которые существуют внутри сцены:"
@@ -9138,11 +9173,12 @@ msgstr ""
 "бесплатно."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
+#, fuzzy
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 "С учетом этого давайте подключим ``GUI`` к ``Player``. Щелкните на узле "
 "``Player`` в панели сцен, чтобы выбрать его. Направляйтесь а инспектор и "
@@ -9252,21 +9288,23 @@ msgid "Godot writes the callback method for you and takes you to it"
 msgstr "Godot напишет метод обратного вызова для вас и доставит вас к нему"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
+#, fuzzy
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 "В скобках после имени функции добавьте аргумент ``player_health``. Когда "
 "игрок излучает сигнал ``health_changed``, он посылает его текущее ``health`` "
 "вместе с ним. Код должен выглядеть так:"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
+#, fuzzy
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 "Обработчик не преобразует PascalCase в snake_case, для примеров C# мы будем "
 "использовать PascalCase для имен методов и camelCase для параметров метода, "
@@ -9285,7 +9323,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 #, fuzzy
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 "Внутри `` _on_Player_health_changed`` давайте вызовим вторую функцию под "
@@ -9333,9 +9371,10 @@ msgid "set the ``TextureProgress``'s ``value`` to ``new_value``"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
+#, fuzzy
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 "``str`` – это встроенная функция, которая преобразует значение в текст. "
@@ -9369,7 +9408,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -9518,7 +9557,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -9533,7 +9572,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -9611,7 +9650,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -9638,7 +9677,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -9775,9 +9814,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -9846,16 +9885,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -9872,14 +9911,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -9913,16 +9952,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -9984,7 +10023,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -10015,7 +10054,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -10161,7 +10200,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -10191,7 +10230,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -10223,7 +10262,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -10660,9 +10699,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -10975,7 +11014,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -11055,7 +11094,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -11172,12 +11211,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -11229,7 +11268,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -12741,7 +12780,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -13123,7 +13162,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -13202,7 +13241,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -13228,7 +13267,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -13448,9 +13487,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -13495,7 +13534,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -13541,7 +13580,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -13552,7 +13591,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -13623,7 +13662,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -13643,7 +13682,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -22208,7 +22247,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "Инструменты"
 
@@ -25152,8 +25191,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -25366,9 +25404,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -27375,7 +27413,7 @@ msgstr ":ref:`AnimatedSprite <class_AnimatedSprite>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
 #, fuzzy
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ":ref:`AnimatedSprite <class_AnimatedSprite>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -28110,437 +28148,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -30306,7 +29913,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -30316,7 +29923,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -45772,9 +45379,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -45824,9 +45431,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -45881,47 +45488,45 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 #, fuzzy
 msgid "Coloring the planet"
 msgstr "Настройка проекта"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -45929,7 +45534,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -45938,7 +45543,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -45946,7 +45551,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -45956,7 +45561,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -45967,19 +45572,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -45987,13 +45592,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -46001,7 +45606,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -46010,7 +45615,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -46024,7 +45629,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -46033,7 +45638,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -46041,10 +45646,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -47041,6 +46646,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -49964,6 +49574,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr "Сеть"
@@ -54676,11 +54712,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -54874,46 +54910,42 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 #, fuzzy
 msgid "Setting up the project"
 msgstr "Настройка вашего проекта"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -54923,29 +54955,30 @@ msgstr ""
 "`демонстрационные проекты Godot <https://github.com/godotengine/godot-demo-"
 "projects>`_."
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -54953,131 +54986,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr "Создание простого плагина"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -55085,56 +55114,56 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 #, fuzzy
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr "Чтобы начать объявлять переменные объекта понадобится:"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -55145,22 +55174,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -55169,7 +55198,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -55177,11 +55206,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -55190,42 +55219,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -55235,7 +55271,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -55244,7 +55280,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -55252,58 +55288,256 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+#, fuzzy
+msgid "Adding properties"
+msgstr "Это его редактируемые свойства."
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -57397,7 +57631,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -57405,18 +57639,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -57424,23 +57658,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -57448,35 +57682,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -57485,103 +57719,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -57589,20 +57823,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -57641,11 +57875,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -57655,24 +57901,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -57681,7 +57927,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -57689,18 +57935,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -57710,7 +57956,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -57719,37 +57965,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -57757,63 +58003,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -57821,13 +58067,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -57835,7 +58081,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -57843,25 +58089,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -57869,30 +58115,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -57900,7 +58146,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -57909,25 +58155,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -57938,46 +58184,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -57986,68 +58232,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -58055,7 +58301,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -58064,11 +58310,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -58076,114 +58322,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -58250,37 +58496,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -58288,61 +58534,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -58362,18 +58608,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -58381,11 +58627,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -58393,37 +58639,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -58484,27 +58730,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -58512,24 +58758,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -58537,29 +58770,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -58567,35 +58800,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -58603,40 +58836,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -58644,131 +58877,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -58788,29 +59021,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -58821,17 +59054,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "Запустить"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -58941,6 +59174,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -59025,61 +59262,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -59088,13 +59325,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -59103,11 +59340,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -59115,14 +59352,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -59130,14 +59367,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -59146,14 +59383,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -59163,7 +59400,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -59172,7 +59409,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -59181,7 +59418,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -59212,7 +59449,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -59222,7 +59459,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -59230,14 +59467,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -59245,21 +59482,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -59268,7 +59505,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -59278,7 +59515,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/sk.po b/weblate/sk.po
index eaf2eae180..23e19abf7d 100644
--- a/weblate/sk.po
+++ b/weblate/sk.po
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-06-15 17:43+0000\n"
 "Last-Translator: MineGame 159 <minegame459@gmail.com>\n"
 "Language-Team: Slovak <https://hosted.weblate.org/projects/godot-engine/"
@@ -64,9 +64,9 @@ msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 
 #: ../../docs/index.rst:43
@@ -132,7 +132,6 @@ msgstr ""
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -151,6 +150,7 @@ msgstr ""
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -291,9 +291,9 @@ msgstr ""
 
 #: ../../docs/about/introduction.rst:85
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1234,7 +1234,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1701,7 +1701,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1776,13 +1776,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2026,8 +2026,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2051,7 +2051,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2125,7 +2125,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2139,7 +2139,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2479,6 +2479,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr ""
@@ -2949,7 +2950,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3075,7 +3076,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3284,7 +3285,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3382,7 +3383,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3410,7 +3411,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -3908,7 +3909,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -3964,8 +3965,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4041,7 +4042,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4138,7 +4139,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4224,14 +4225,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4340,7 +4341,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4386,7 +4387,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4426,7 +4427,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4467,9 +4468,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4557,7 +4558,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4674,7 +4675,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4722,7 +4723,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4864,7 +4865,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -4972,7 +4973,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -4996,7 +4997,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5323,9 +5324,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5355,8 +5357,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5396,8 +5399,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6299,7 +6302,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6368,9 +6371,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6387,12 +6390,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6415,8 +6418,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6592,10 +6596,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6674,16 +6678,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6694,7 +6698,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6736,7 +6740,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6763,7 +6767,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -6912,7 +6916,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -6927,7 +6931,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7005,7 +7009,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7032,7 +7036,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7169,9 +7173,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7240,16 +7244,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7266,14 +7270,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7304,16 +7308,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7375,7 +7379,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7405,7 +7409,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7551,7 +7555,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7581,7 +7585,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7613,7 +7617,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8048,9 +8052,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8359,7 +8363,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8439,7 +8443,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8556,12 +8560,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8613,7 +8617,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10048,7 +10052,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10428,7 +10432,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10507,7 +10511,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10533,7 +10537,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10744,9 +10748,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10791,7 +10795,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10837,7 +10841,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10848,7 +10852,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -10919,7 +10923,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -10939,7 +10943,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19312,7 +19316,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -22246,8 +22250,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22460,9 +22463,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24446,7 +24449,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25177,437 +25180,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27373,7 +26945,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27383,7 +26955,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42676,9 +42248,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42728,9 +42300,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42784,46 +42356,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42831,7 +42401,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42840,7 +42410,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42848,7 +42418,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42858,7 +42428,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -42869,19 +42439,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -42889,13 +42459,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -42903,7 +42473,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -42912,7 +42482,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -42926,7 +42496,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -42935,7 +42505,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -42943,10 +42513,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -43911,6 +43481,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46826,6 +46401,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51370,11 +51371,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51568,73 +51569,70 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51642,131 +51640,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51774,55 +51768,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51833,22 +51827,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51857,7 +51851,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -51865,11 +51859,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -51878,42 +51872,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -51923,7 +51924,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -51932,7 +51933,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -51940,58 +51941,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54081,7 +54279,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54089,18 +54287,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54108,23 +54306,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54132,35 +54330,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54169,103 +54367,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54273,20 +54471,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54325,11 +54523,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54339,24 +54549,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54365,7 +54575,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54373,18 +54583,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54394,7 +54604,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54403,37 +54613,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54441,63 +54651,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54505,13 +54715,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54519,7 +54729,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54527,25 +54737,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54553,30 +54763,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54584,7 +54794,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54593,25 +54803,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54622,46 +54832,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54670,68 +54880,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54739,7 +54949,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54748,11 +54958,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54760,114 +54970,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -54934,37 +55144,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -54972,61 +55182,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55046,18 +55256,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55065,11 +55275,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55077,37 +55287,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55168,27 +55378,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55196,24 +55406,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55221,29 +55418,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55251,35 +55448,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55287,40 +55484,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55328,131 +55525,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55472,29 +55669,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55505,17 +55702,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55625,6 +55822,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55709,61 +55910,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55772,13 +55973,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55787,11 +55988,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55799,14 +56000,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55814,14 +56015,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55830,14 +56031,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55847,7 +56048,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55856,7 +56057,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -55865,7 +56066,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -55896,7 +56097,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -55906,7 +56107,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -55914,14 +56115,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -55929,21 +56130,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -55952,7 +56153,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -55962,7 +56163,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/sl.po b/weblate/sl.po
index 0d2933598d..2fd1d9447a 100644
--- a/weblate/sl.po
+++ b/weblate/sl.po
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-06-26 13:44+0000\n"
 "Last-Translator: matevž lapajne <sivar.lapajne@gmail.com>\n"
 "Language-Team: Slovenian <https://hosted.weblate.org/projects/godot-engine/"
@@ -62,9 +62,9 @@ msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 
 #: ../../docs/index.rst:43
@@ -130,7 +130,6 @@ msgstr "O Programu"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -149,6 +148,7 @@ msgstr "O Programu"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -342,10 +342,11 @@ msgstr ""
 "pogon, razvijati C++ module ali vtičnike za urejevalnik."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1378,7 +1379,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1845,7 +1846,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1920,13 +1921,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2170,8 +2171,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2195,7 +2196,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2269,7 +2270,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2283,7 +2284,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2623,6 +2624,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Signali"
@@ -3094,7 +3096,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3220,7 +3222,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3431,7 +3433,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3529,7 +3531,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3557,7 +3559,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -4055,7 +4057,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4112,8 +4114,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4189,7 +4191,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4286,7 +4288,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4372,14 +4374,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4488,7 +4490,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4534,7 +4536,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4574,7 +4576,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4615,9 +4617,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4705,7 +4707,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4822,7 +4824,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4870,7 +4872,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -5012,7 +5014,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5120,7 +5122,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5144,7 +5146,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5471,9 +5473,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5503,8 +5506,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5544,8 +5548,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6447,7 +6451,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6516,9 +6520,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6535,12 +6539,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6563,8 +6567,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6740,10 +6745,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6822,16 +6827,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6842,7 +6847,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6884,7 +6889,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6911,7 +6916,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -7060,7 +7065,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7075,7 +7080,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7153,7 +7158,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7180,7 +7185,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7317,9 +7322,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7388,16 +7393,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7414,14 +7419,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7452,16 +7457,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7523,7 +7528,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7553,7 +7558,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7699,7 +7704,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7729,7 +7734,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7761,7 +7766,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8196,9 +8201,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8508,7 +8513,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8588,7 +8593,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8705,12 +8710,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8762,7 +8767,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10200,7 +10205,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10580,7 +10585,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10659,7 +10664,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10685,7 +10690,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10897,9 +10902,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10944,7 +10949,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10990,7 +10995,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -11001,7 +11006,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11072,7 +11077,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11092,7 +11097,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19475,7 +19480,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "Orodja"
 
@@ -22410,8 +22415,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22624,9 +22628,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24613,7 +24617,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25344,437 +25348,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27540,7 +27113,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27550,7 +27123,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42846,9 +42419,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42898,9 +42471,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42954,46 +42527,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -43001,7 +42572,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -43010,7 +42581,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -43018,7 +42589,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -43028,7 +42599,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -43039,19 +42610,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -43059,13 +42630,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43073,7 +42644,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43082,7 +42653,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43096,7 +42667,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43105,7 +42676,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43113,10 +42684,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44081,6 +43652,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46996,6 +46572,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51541,11 +51543,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51739,45 +51741,41 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -51786,29 +51784,30 @@ msgstr ""
 "Poleg te dokumentacije si boste morda tudi želeli pogledati različne `Godot "
 "demo projekti <https://github.com/godotengine/godot-demo-projects>`_."
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51816,131 +51815,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51948,55 +51943,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -52007,22 +52002,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -52031,7 +52026,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -52039,11 +52034,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -52052,42 +52047,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52097,7 +52099,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52106,7 +52108,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52114,58 +52116,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54256,7 +54455,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54264,18 +54463,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54283,23 +54482,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54307,35 +54506,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54344,103 +54543,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54448,20 +54647,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54500,11 +54699,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54514,24 +54725,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54540,7 +54751,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54548,18 +54759,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54569,7 +54780,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54578,37 +54789,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54616,63 +54827,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54680,13 +54891,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54694,7 +54905,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54702,25 +54913,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54728,30 +54939,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54759,7 +54970,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54768,25 +54979,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54797,46 +55008,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54845,68 +55056,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54914,7 +55125,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54923,11 +55134,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54935,114 +55146,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55109,37 +55320,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55147,61 +55358,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55221,18 +55432,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55240,11 +55451,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55252,37 +55463,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55343,27 +55554,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55371,24 +55582,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55396,29 +55594,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55426,35 +55624,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55462,40 +55660,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55503,131 +55701,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55647,29 +55845,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55680,17 +55878,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "Zaženi"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55800,6 +55998,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55884,61 +56086,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55947,13 +56149,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55962,11 +56164,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55974,14 +56176,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55989,14 +56191,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -56005,14 +56207,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -56022,7 +56224,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -56031,7 +56233,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -56040,7 +56242,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56071,7 +56273,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56081,7 +56283,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56089,14 +56291,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56104,21 +56306,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56127,7 +56329,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56137,7 +56339,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/sr_Latn.po b/weblate/sr_Latn.po
index ee53783d13..be00fd1501 100644
--- a/weblate/sr_Latn.po
+++ b/weblate/sr_Latn.po
@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-09-21 20:35+0000\n"
 "Last-Translator: BLu <blmasfon@gmail.com>\n"
 "Language-Team: Serbian (latin) <https://hosted.weblate.org/projects/godot-"
@@ -67,9 +67,9 @@ msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 
 #: ../../docs/index.rst:43
@@ -135,7 +135,6 @@ msgstr ""
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -154,6 +153,7 @@ msgstr ""
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -352,10 +352,11 @@ msgstr ""
 "igre, razvijanju C++ modula i dodataka za pregledač."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1341,7 +1342,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1808,7 +1809,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1883,13 +1884,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2133,8 +2134,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2158,7 +2159,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2232,7 +2233,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2246,7 +2247,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2586,6 +2587,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr ""
@@ -3056,7 +3058,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3182,7 +3184,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3391,7 +3393,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3489,7 +3491,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3517,7 +3519,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -4015,7 +4017,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4071,8 +4073,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4148,7 +4150,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4245,7 +4247,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4331,14 +4333,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4447,7 +4449,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4493,7 +4495,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4533,7 +4535,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4574,9 +4576,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4664,7 +4666,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4781,7 +4783,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4829,7 +4831,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4971,7 +4973,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5079,7 +5081,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5103,7 +5105,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5430,9 +5432,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5462,8 +5465,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5503,8 +5507,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6406,7 +6410,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6475,9 +6479,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6494,12 +6498,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6522,8 +6526,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6699,10 +6704,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6781,16 +6786,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6801,7 +6806,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6843,7 +6848,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6870,7 +6875,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -7019,7 +7024,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7034,7 +7039,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7112,7 +7117,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7139,7 +7144,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7276,9 +7281,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7347,16 +7352,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7373,14 +7378,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7411,16 +7416,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7482,7 +7487,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7512,7 +7517,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7658,7 +7663,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7688,7 +7693,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7720,7 +7725,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8155,9 +8160,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8467,7 +8472,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8547,7 +8552,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8664,12 +8669,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8721,7 +8726,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10157,7 +10162,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10537,7 +10542,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10616,7 +10621,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10642,7 +10647,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10854,9 +10859,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10901,7 +10906,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10947,7 +10952,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10958,7 +10963,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11029,7 +11034,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11049,7 +11054,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19424,7 +19429,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -22358,8 +22363,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22572,9 +22576,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24559,7 +24563,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25290,437 +25294,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27486,7 +27059,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27496,7 +27069,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42789,9 +42362,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42841,9 +42414,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42897,46 +42470,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42944,7 +42515,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42953,7 +42524,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42961,7 +42532,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42971,7 +42542,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -42982,19 +42553,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -43002,13 +42573,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43016,7 +42587,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43025,7 +42596,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43039,7 +42610,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43048,7 +42619,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43056,10 +42627,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44024,6 +43595,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46939,6 +46515,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51483,11 +51485,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51681,45 +51683,41 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -51728,29 +51726,30 @@ msgstr ""
 "Uz ovu dokumentaciju takođe možete pogledati raznorazne `Godot demo projects "
 "<https://github.com/godotengine/godot-demo-projects>`_."
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51758,131 +51757,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51890,55 +51885,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51949,22 +51944,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51973,7 +51968,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -51981,11 +51976,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -51994,42 +51989,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52039,7 +52041,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52048,7 +52050,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52056,58 +52058,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54198,7 +54397,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54206,18 +54405,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54225,23 +54424,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54249,35 +54448,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54286,103 +54485,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54390,20 +54589,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54442,11 +54641,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54456,24 +54667,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54482,7 +54693,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54490,18 +54701,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54511,7 +54722,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54520,37 +54731,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54558,63 +54769,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54622,13 +54833,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54636,7 +54847,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54644,25 +54855,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54670,30 +54881,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54701,7 +54912,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54710,25 +54921,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54739,46 +54950,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54787,68 +54998,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54856,7 +55067,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54865,11 +55076,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54877,114 +55088,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55051,37 +55262,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55089,61 +55300,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55163,18 +55374,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55182,11 +55393,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55194,37 +55405,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55285,27 +55496,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55313,24 +55524,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55338,29 +55536,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55368,35 +55566,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55404,40 +55602,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55445,131 +55643,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55589,29 +55787,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55622,17 +55820,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55742,6 +55940,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55826,61 +56028,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55889,13 +56091,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55904,11 +56106,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55916,14 +56118,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55931,14 +56133,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55947,14 +56149,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55964,7 +56166,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55973,7 +56175,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -55982,7 +56184,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56013,7 +56215,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56023,7 +56225,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56031,14 +56233,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56046,21 +56248,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56069,7 +56271,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56079,7 +56281,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/sv.po b/weblate/sv.po
index a755c54709..1d0336361d 100644
--- a/weblate/sv.po
+++ b/weblate/sv.po
@@ -13,7 +13,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-10-03 05:37+0000\n"
 "Last-Translator: Christoffer Sundbom <christoffer_karlsson@live.se>\n"
 "Language-Team: Swedish <https://hosted.weblate.org/projects/godot-engine/"
@@ -78,13 +78,14 @@ msgstr ""
 "hör av dig så vi kan förbättra den!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Skicka in issues och pull requests till vår `GitHub repository <https://"
 "github.com/godotengine/godot-docs/issues>` _, hjälp oss `översätta "
@@ -157,7 +158,6 @@ msgstr "Om"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -176,6 +176,7 @@ msgstr "Om"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -374,10 +375,11 @@ msgstr ""
 "spelmotorn samt utvecklar C++ moduler och plugins."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1394,7 +1396,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1861,7 +1863,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1936,13 +1938,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2186,8 +2188,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2211,7 +2213,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2285,7 +2287,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2299,7 +2301,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2639,6 +2641,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr ""
@@ -3109,7 +3112,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3235,7 +3238,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3444,7 +3447,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3542,7 +3545,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3570,7 +3573,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -4068,7 +4071,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4124,8 +4127,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4201,7 +4204,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4298,7 +4301,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4384,14 +4387,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4501,7 +4504,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4547,7 +4550,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4587,7 +4590,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4628,9 +4631,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4718,7 +4721,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4835,7 +4838,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4883,7 +4886,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -5025,7 +5028,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5133,7 +5136,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5157,7 +5160,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5484,9 +5487,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5516,8 +5520,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5557,8 +5562,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6460,7 +6465,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6529,9 +6534,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6551,13 +6556,14 @@ msgstr ""
 "`end`."
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
+#, fuzzy
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 "Läs in projektet ``start`` i Godot. I rutan ``FileSystem`` dubbelklicka på "
 "LevelMockup.tscn för att öppna den. Det är en mockup för ett RPG-spel där "
@@ -6592,9 +6598,11 @@ msgid "The scene tree, with the GUI scene set to display its children"
 msgstr "Scen-trädet med GUI-scenen som visar dess underliggande noder"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
+#, fuzzy
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 "GUI-scenen samlar alla delar av gränssnittet. Den kommer med ett "
 "grundläggande skript där vi får sökvägen till noder som finns inuti scenen:"
@@ -6780,10 +6788,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6862,16 +6870,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6882,7 +6890,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6924,7 +6932,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6951,7 +6959,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -7100,7 +7108,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7115,7 +7123,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7193,7 +7201,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7220,7 +7228,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7357,9 +7365,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7428,16 +7436,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7454,14 +7462,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7492,16 +7500,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7563,7 +7571,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7593,7 +7601,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7739,7 +7747,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7769,7 +7777,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7801,7 +7809,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8236,9 +8244,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8547,7 +8555,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8627,7 +8635,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8744,12 +8752,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8801,7 +8809,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10237,7 +10245,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10617,7 +10625,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10696,7 +10704,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10722,7 +10730,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10933,9 +10941,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10980,7 +10988,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -11026,7 +11034,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -11037,7 +11045,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11108,7 +11116,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11128,7 +11136,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19504,7 +19512,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -22438,8 +22446,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22652,9 +22659,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24639,7 +24646,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25370,437 +25377,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27566,7 +27142,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27576,7 +27152,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42871,9 +42447,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42923,9 +42499,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42979,46 +42555,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -43026,7 +42600,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -43035,7 +42609,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -43043,7 +42617,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -43053,7 +42627,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -43064,19 +42638,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -43084,13 +42658,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43098,7 +42672,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43107,7 +42681,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43121,7 +42695,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43130,7 +42704,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43138,10 +42712,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44106,6 +43680,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -47022,6 +46601,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51566,11 +51571,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51764,73 +51769,70 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51838,131 +51840,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51970,55 +51968,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -52029,22 +52027,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -52053,7 +52051,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -52061,11 +52059,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -52074,42 +52072,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52119,7 +52124,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52128,7 +52133,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52136,58 +52141,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54277,7 +54479,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54285,18 +54487,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54304,23 +54506,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54328,35 +54530,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54365,103 +54567,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54469,20 +54671,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54521,11 +54723,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54535,24 +54749,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54561,7 +54775,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54569,18 +54783,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54590,7 +54804,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54599,37 +54813,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54637,63 +54851,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54701,13 +54915,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54715,7 +54929,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54723,25 +54937,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54749,30 +54963,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54780,7 +54994,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54789,25 +55003,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54818,46 +55032,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54866,68 +55080,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54935,7 +55149,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54944,11 +55158,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54956,114 +55170,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55130,37 +55344,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55168,61 +55382,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55242,18 +55456,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55261,11 +55475,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55273,37 +55487,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55364,27 +55578,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55392,24 +55606,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55417,29 +55618,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55447,35 +55648,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55483,40 +55684,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55524,131 +55725,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55668,29 +55869,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55701,17 +55902,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55821,6 +56022,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55905,61 +56110,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55968,13 +56173,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55983,11 +56188,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55995,14 +56200,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -56010,14 +56215,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -56026,14 +56231,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -56043,7 +56248,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -56052,7 +56257,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -56061,7 +56266,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56092,7 +56297,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56102,7 +56307,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56110,14 +56315,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56125,21 +56330,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56148,7 +56353,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56158,7 +56363,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/te.po b/weblate/te.po
index 17f9b3ecf2..1fa50b8cc0 100644
--- a/weblate/te.po
+++ b/weblate/te.po
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-10-11 08:35+0000\n"
 "Last-Translator: Chanda Venkata Ramana Moorthy <moorthyworks@gmail.com>\n"
 "Language-Team: Telugu <https://hosted.weblate.org/projects/godot-engine/"
@@ -74,9 +74,9 @@ msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 
 #: ../../docs/index.rst:43
@@ -143,7 +143,6 @@ msgstr "గురించి"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -162,6 +161,7 @@ msgstr "గురించి"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -302,9 +302,9 @@ msgstr ""
 
 #: ../../docs/about/introduction.rst:85
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1245,7 +1245,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1712,7 +1712,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1787,13 +1787,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2037,8 +2037,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2062,7 +2062,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2136,7 +2136,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2150,7 +2150,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2490,6 +2490,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr ""
@@ -2960,7 +2961,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3086,7 +3087,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3295,7 +3296,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3393,7 +3394,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3421,7 +3422,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -3919,7 +3920,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -3975,8 +3976,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4052,7 +4053,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4149,7 +4150,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4235,14 +4236,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4351,7 +4352,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4397,7 +4398,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4437,7 +4438,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4478,9 +4479,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4568,7 +4569,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4685,7 +4686,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4733,7 +4734,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4875,7 +4876,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -4983,7 +4984,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5007,7 +5008,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5334,9 +5335,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5366,8 +5368,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5407,8 +5410,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6310,7 +6313,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6379,9 +6382,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6398,12 +6401,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6426,8 +6429,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6603,10 +6607,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6685,16 +6689,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6705,7 +6709,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6747,7 +6751,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6774,7 +6778,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -6923,7 +6927,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -6938,7 +6942,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7016,7 +7020,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7043,7 +7047,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7180,9 +7184,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7251,16 +7255,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7277,14 +7281,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7315,16 +7319,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7386,7 +7390,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7416,7 +7420,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7562,7 +7566,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7592,7 +7596,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7624,7 +7628,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8059,9 +8063,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8370,7 +8374,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8450,7 +8454,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8567,12 +8571,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8624,7 +8628,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10059,7 +10063,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10439,7 +10443,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10518,7 +10522,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10544,7 +10548,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10755,9 +10759,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10802,7 +10806,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10848,7 +10852,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10859,7 +10863,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -10930,7 +10934,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -10950,7 +10954,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19324,7 +19328,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -22258,8 +22262,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22472,9 +22475,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24459,7 +24462,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25190,437 +25193,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27386,7 +26958,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27396,7 +26968,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42690,9 +42262,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42742,9 +42314,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42798,46 +42370,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42845,7 +42415,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42854,7 +42424,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42862,7 +42432,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42872,7 +42442,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -42883,19 +42453,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -42903,13 +42473,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -42917,7 +42487,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -42926,7 +42496,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -42940,7 +42510,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -42949,7 +42519,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -42957,10 +42527,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -43925,6 +43495,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46840,6 +46415,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51384,11 +51385,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51582,73 +51583,70 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51656,131 +51654,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51788,55 +51782,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51847,22 +51841,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51871,7 +51865,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -51879,11 +51873,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -51892,42 +51886,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -51937,7 +51938,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -51946,7 +51947,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -51954,58 +51955,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54095,7 +54293,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54103,18 +54301,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54122,23 +54320,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54146,35 +54344,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54183,103 +54381,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54287,20 +54485,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54339,11 +54537,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54353,24 +54563,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54379,7 +54589,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54387,18 +54597,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54408,7 +54618,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54417,37 +54627,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54455,63 +54665,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54519,13 +54729,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54533,7 +54743,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54541,25 +54751,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54567,30 +54777,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54598,7 +54808,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54607,25 +54817,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54636,46 +54846,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54684,68 +54894,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54753,7 +54963,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54762,11 +54972,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54774,114 +54984,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -54948,37 +55158,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -54986,61 +55196,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55060,18 +55270,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55079,11 +55289,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55091,37 +55301,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55182,27 +55392,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55210,24 +55420,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55235,29 +55432,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55265,35 +55462,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55301,40 +55498,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55342,131 +55539,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55486,29 +55683,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55519,17 +55716,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55639,6 +55836,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55723,61 +55924,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55786,13 +55987,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55801,11 +56002,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55813,14 +56014,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55828,14 +56029,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55844,14 +56045,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55861,7 +56062,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55870,7 +56071,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -55879,7 +56080,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -55910,7 +56111,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -55920,7 +56121,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -55928,14 +56129,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -55943,21 +56144,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -55966,7 +56167,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -55976,7 +56177,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/th.po b/weblate/th.po
index 5b01915b8f..5332b8ea42 100644
--- a/weblate/th.po
+++ b/weblate/th.po
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-04-17 12:41+0000\n"
 "Last-Translator: Poommetee Ketson <poommetee@protonmail.com>\n"
 "Language-Team: Thai <https://hosted.weblate.org/projects/godot-engine/godot-"
@@ -61,9 +61,9 @@ msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 
 #: ../../docs/index.rst:43
@@ -129,7 +129,6 @@ msgstr "เกี่ยวกับ"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -148,6 +147,7 @@ msgstr "เกี่ยวกับ"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -330,10 +330,11 @@ msgstr ""
 "โดยมีข้อมูลเกี่ยวกับการคอมไพล์เอ็นจิ้น การสร้างโมดูลหรือปลั๊กอินด้วยภาษา C++"
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1388,7 +1389,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1856,7 +1857,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1931,13 +1932,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2181,8 +2182,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2206,7 +2207,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2280,7 +2281,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2294,7 +2295,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2634,6 +2635,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "สัญญาณ"
@@ -3105,7 +3107,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3231,7 +3233,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3442,7 +3444,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3541,7 +3543,7 @@ msgstr "การใช้ใน GDScript"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3569,7 +3571,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -4067,7 +4069,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4123,8 +4125,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4200,7 +4202,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4297,7 +4299,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4383,14 +4385,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4499,7 +4501,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4545,7 +4547,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4585,7 +4587,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4626,9 +4628,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4716,7 +4718,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4833,7 +4835,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4881,7 +4883,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -5023,7 +5025,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5131,7 +5133,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5155,7 +5157,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5482,9 +5484,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5514,8 +5517,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5555,8 +5559,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6458,7 +6462,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6527,9 +6531,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6546,12 +6550,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6574,8 +6578,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6751,10 +6756,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6833,16 +6838,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6853,7 +6858,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6895,7 +6900,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6922,7 +6927,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -7071,7 +7076,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7086,7 +7091,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7164,7 +7169,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7191,7 +7196,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7328,9 +7333,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7399,16 +7404,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7425,14 +7430,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7463,16 +7468,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7534,7 +7539,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7564,7 +7569,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7710,7 +7715,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7740,7 +7745,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7772,7 +7777,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8207,9 +8212,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8520,7 +8525,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8600,7 +8605,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8717,12 +8722,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8774,7 +8779,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10216,7 +10221,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10596,7 +10601,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10675,7 +10680,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10701,7 +10706,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10913,9 +10918,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10960,7 +10965,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -11006,7 +11011,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -11017,7 +11022,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11088,7 +11093,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11108,7 +11113,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19539,7 +19544,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -22480,8 +22485,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22694,9 +22698,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24684,7 +24688,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25416,437 +25420,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27612,7 +27185,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27622,7 +27195,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42915,9 +42488,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42967,9 +42540,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -43023,46 +42596,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -43070,7 +42641,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -43079,7 +42650,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -43087,7 +42658,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -43097,7 +42668,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -43108,19 +42679,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -43128,13 +42699,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43142,7 +42713,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43151,7 +42722,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43165,7 +42736,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43174,7 +42745,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43182,10 +42753,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44150,6 +43721,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -47066,6 +46642,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51610,11 +51612,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51808,45 +51810,41 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -51855,29 +51853,30 @@ msgstr ""
 "นอกจากนี้ท่านอาจสนใจเกี่ยวกับ `ตัวอย่างโปรเจกต์ <https://github.com/godotengine/godot-"
 "demo-projects>`_"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51885,131 +51884,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -52017,55 +52012,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -52076,22 +52071,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -52100,7 +52095,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -52108,11 +52103,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -52121,42 +52116,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52166,7 +52168,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52175,7 +52177,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52183,58 +52185,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54326,7 +54525,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54334,18 +54533,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54353,23 +54552,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54377,35 +54576,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54414,103 +54613,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54518,20 +54717,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54570,11 +54769,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54584,24 +54795,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54610,7 +54821,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54618,18 +54829,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54639,7 +54850,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54648,37 +54859,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54686,63 +54897,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54750,13 +54961,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54764,7 +54975,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54772,25 +54983,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54798,30 +55009,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54829,7 +55040,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54838,25 +55049,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54867,46 +55078,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54915,68 +55126,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54984,7 +55195,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54993,11 +55204,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -55005,114 +55216,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55179,37 +55390,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55217,61 +55428,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55291,18 +55502,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55310,11 +55521,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55322,37 +55533,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55413,27 +55624,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55441,24 +55652,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55466,29 +55664,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55496,35 +55694,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55532,40 +55730,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55573,131 +55771,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55717,29 +55915,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55750,17 +55948,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55870,6 +56068,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55954,61 +56156,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -56017,13 +56219,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -56032,11 +56234,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -56044,14 +56246,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -56059,14 +56261,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -56075,14 +56277,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -56092,7 +56294,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -56101,7 +56303,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -56110,7 +56312,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56141,7 +56343,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56151,7 +56353,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56159,14 +56361,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56174,21 +56376,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56197,7 +56399,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56207,7 +56409,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/tr.po b/weblate/tr.po
index 349553665e..d234d8a239 100644
--- a/weblate/tr.po
+++ b/weblate/tr.po
@@ -16,7 +16,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-11-07 15:09+0000\n"
 "Last-Translator: Oğuzhan Özdemir <ozdemiroguzhan0@gmail.com>\n"
 "Language-Team: Turkish <https://hosted.weblate.org/projects/godot-engine/"
@@ -84,9 +84,9 @@ msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 
 #: ../../docs/index.rst:43
@@ -152,7 +152,6 @@ msgstr "Hakkında"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -171,6 +170,7 @@ msgstr "Hakkında"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -346,9 +346,9 @@ msgstr ""
 
 #: ../../docs/about/introduction.rst:85
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1304,7 +1304,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1771,7 +1771,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1846,13 +1846,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2096,8 +2096,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2121,7 +2121,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2195,7 +2195,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2209,7 +2209,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2549,6 +2549,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Sinyaller"
@@ -3021,7 +3022,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3148,7 +3149,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3360,7 +3361,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3458,7 +3459,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3486,7 +3487,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -3985,7 +3986,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4042,8 +4043,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4119,7 +4120,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4216,7 +4217,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4302,14 +4303,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4419,7 +4420,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4465,7 +4466,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4505,7 +4506,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4546,9 +4547,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4636,7 +4637,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4753,7 +4754,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4801,7 +4802,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -4943,7 +4944,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5051,7 +5052,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5075,7 +5076,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5402,9 +5403,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5434,8 +5436,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5475,8 +5478,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6378,7 +6381,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6447,9 +6450,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6466,12 +6469,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6494,8 +6497,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6671,10 +6675,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6753,16 +6757,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6773,7 +6777,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6815,7 +6819,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6842,7 +6846,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -6991,7 +6995,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7006,7 +7010,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7084,7 +7088,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7111,7 +7115,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7248,9 +7252,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7319,16 +7323,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7345,14 +7349,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7383,16 +7387,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7454,7 +7458,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7484,7 +7488,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7630,7 +7634,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7660,7 +7664,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7692,7 +7696,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8127,9 +8131,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8439,7 +8443,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8519,7 +8523,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8636,12 +8640,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8693,7 +8697,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10134,7 +10138,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10514,7 +10518,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10593,7 +10597,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10619,7 +10623,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10830,9 +10834,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10877,7 +10881,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -10923,7 +10927,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -10934,7 +10938,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11005,7 +11009,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11025,7 +11029,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19412,7 +19416,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "Araçlar"
 
@@ -22349,8 +22353,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22563,9 +22566,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24553,7 +24556,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25285,437 +25288,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27481,7 +27053,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27491,7 +27063,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42788,9 +42360,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42840,9 +42412,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42896,46 +42468,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -42943,7 +42513,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -42952,7 +42522,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -42960,7 +42530,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -42970,7 +42540,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -42981,19 +42551,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -43001,13 +42571,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43015,7 +42585,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43024,7 +42594,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43038,7 +42608,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43047,7 +42617,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43055,10 +42625,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44023,6 +43593,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -46941,6 +46516,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51486,11 +51487,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51684,73 +51685,70 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51758,131 +51756,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51890,55 +51884,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -51949,22 +51943,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -51973,7 +51967,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -51981,11 +51975,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -51994,42 +51988,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52039,7 +52040,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52048,7 +52049,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52056,58 +52057,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54198,7 +54396,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54206,18 +54404,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54225,23 +54423,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54249,35 +54447,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54286,103 +54484,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54390,20 +54588,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54442,11 +54640,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54456,24 +54666,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54482,7 +54692,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54490,18 +54700,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54511,7 +54721,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54520,37 +54730,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54558,63 +54768,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54622,13 +54832,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54636,7 +54846,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54644,25 +54854,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54670,30 +54880,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54701,7 +54911,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54710,25 +54920,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54739,46 +54949,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54787,68 +54997,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54856,7 +55066,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54865,11 +55075,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54877,114 +55087,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55051,37 +55261,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55089,61 +55299,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55163,18 +55373,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55182,11 +55392,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55194,37 +55404,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55285,27 +55495,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55313,24 +55523,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55338,29 +55535,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55368,35 +55565,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55404,40 +55601,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55445,131 +55642,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55589,29 +55786,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55622,17 +55819,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "Çalıştır"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55742,6 +55939,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55826,61 +56027,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55889,13 +56090,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55904,11 +56105,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -55916,14 +56117,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -55931,14 +56132,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -55947,14 +56148,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -55964,7 +56165,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -55973,7 +56174,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -55982,7 +56183,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56013,7 +56214,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56023,7 +56224,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56031,14 +56232,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56046,21 +56247,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56069,7 +56270,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56079,7 +56280,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/uk.po b/weblate/uk.po
index b50b41da98..d19018278f 100644
--- a/weblate/uk.po
+++ b/weblate/uk.po
@@ -9,7 +9,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Ukrainian (Godot Engine)\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-12-04 22:23+0000\n"
 "Last-Translator: Максим Якимчук <xpinovo@gmail.com>\n"
 "Language-Team: Ukrainian <https://hosted.weblate.org/projects/godot-engine/"
@@ -74,13 +74,14 @@ msgstr ""
 "нам покращити документацію, повідомивши нам про це!"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Надішліть проблему (issue) або потягніть запит (pull request) у `репозиторії "
 "GitHub <https://github.com/godotengine/godot-docs/issues>`_, допоможіть нам "
@@ -152,7 +153,6 @@ msgstr "Про"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -171,6 +171,7 @@ msgstr "Про"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -367,10 +368,11 @@ msgstr ""
 "+ або плаґінів редактора."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1471,7 +1473,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1942,7 +1944,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -2017,13 +2019,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2267,8 +2269,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2292,7 +2294,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2366,7 +2368,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2380,7 +2382,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2720,6 +2722,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Сигнали"
@@ -3197,7 +3200,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3324,7 +3327,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3536,7 +3539,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3634,7 +3637,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3662,7 +3665,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -4163,7 +4166,7 @@ msgstr "Ось повний скрипт для гравця із комента
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4220,8 +4223,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4299,7 +4302,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4396,7 +4399,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4482,14 +4485,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4598,7 +4601,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4644,7 +4647,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4684,7 +4687,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4725,9 +4728,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4815,7 +4818,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4932,7 +4935,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4980,7 +4983,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -5122,7 +5125,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5230,7 +5233,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5254,7 +5257,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5581,9 +5584,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5613,8 +5617,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5654,8 +5659,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6557,7 +6562,7 @@ msgstr "Вступ"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6626,9 +6631,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6645,12 +6650,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6673,8 +6678,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6850,10 +6856,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6932,16 +6938,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6952,7 +6958,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6994,7 +7000,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -7021,7 +7027,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -7170,7 +7176,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7185,7 +7191,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7263,7 +7269,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7290,7 +7296,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7427,9 +7433,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7498,16 +7504,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7524,14 +7530,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7562,16 +7568,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7633,7 +7639,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7664,7 +7670,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7811,7 +7817,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7841,7 +7847,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7873,7 +7879,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8308,9 +8314,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8619,7 +8625,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8699,7 +8705,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8816,12 +8822,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8873,7 +8879,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10315,7 +10321,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10698,7 +10704,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10777,7 +10783,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10803,7 +10809,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -11014,9 +11020,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -11061,7 +11067,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -11107,7 +11113,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -11118,7 +11124,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11189,7 +11195,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11209,7 +11215,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19638,7 +19644,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "Інструменти"
 
@@ -22584,8 +22590,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22798,9 +22803,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24810,7 +24815,7 @@ msgstr ":ref:`RID<class_rid>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
 #, fuzzy
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ":ref:`Color <class_Color>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25544,437 +25549,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27740,7 +27314,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27750,7 +27324,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -43063,9 +42637,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -43115,9 +42689,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -43171,47 +42745,45 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 #, fuzzy
 msgid "Coloring the planet"
 msgstr "Як розпочати гру"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -43219,7 +42791,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -43228,7 +42800,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -43236,7 +42808,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -43246,7 +42818,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -43257,20 +42829,20 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 #, fuzzy
 msgid "Making an ocean"
 msgstr "Внесення змін"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -43278,13 +42850,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43292,7 +42864,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43301,7 +42873,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43315,7 +42887,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43324,7 +42896,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43332,10 +42904,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44303,6 +43875,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -47235,6 +46812,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr "Робота у мережі"
@@ -51783,11 +51786,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr "Компілювання"
 
@@ -51981,46 +51984,42 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 #, fuzzy
 msgid "Setting up the project"
 msgstr "Налаштовування вашого проекту"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -52029,29 +52028,30 @@ msgstr ""
 "Якщо хочете взяти участь у написанні документації, сховище її коду "
 "розташовано `тут <https://github.com/godotengine/godot-docs>`_."
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -52059,131 +52059,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr "Створення простого додатка"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -52191,55 +52187,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -52250,22 +52246,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -52274,7 +52270,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -52282,12 +52278,12 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 #, fuzzy
 msgid "Compiling the plugin"
 msgstr "Компіляція нашого додатка"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -52296,43 +52292,50 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 #, fuzzy
 msgid "Using the GDNative module"
 msgstr "Використання вашого модуля GDNative"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52342,7 +52345,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52351,7 +52354,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52359,58 +52362,256 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+#, fuzzy
+msgid "Adding properties"
+msgstr "Властивості вузла"
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54506,7 +54707,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54519,18 +54720,18 @@ msgstr ""
 "`doc_compiling_for_web`, :ref:`doc_compiling_for_windows` та :ref:"
 "`doc_compiling_for_x11`."
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr "Вибір платформи"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54538,23 +54739,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54562,35 +54763,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54599,103 +54800,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr "Призначення"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr "Біти"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr "Інші параметри збирання"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54703,20 +54904,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54755,11 +54956,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54769,24 +54982,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54795,7 +55008,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54803,18 +55016,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54824,7 +55037,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54833,37 +55046,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54871,63 +55084,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54935,13 +55148,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54949,7 +55162,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54957,25 +55170,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr "Приклад:"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54983,30 +55196,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -55014,7 +55227,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -55023,25 +55236,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -55052,46 +55265,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr "тощо"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -55100,68 +55313,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -55169,7 +55382,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -55178,11 +55391,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -55190,114 +55403,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr "**Arch**"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr "**Debian** / **Ubuntu**"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr "**Fedora**"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr "**macOS**"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr "**Mageia**"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr "Вирішення проблем"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55364,37 +55577,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr "**FreeBSD**"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr "**Gentoo**"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr "OpenBSD"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr "**openSUSE**"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55402,61 +55615,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr "%1 біт"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr "%1 біт"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55477,18 +55690,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55496,11 +55709,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55508,37 +55721,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55599,27 +55812,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55627,24 +55840,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr "Набір інструментів"
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55652,29 +55852,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55682,35 +55882,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55718,40 +55918,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55759,131 +55959,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55903,29 +56103,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55936,17 +56136,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "Запустити"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -56056,6 +56256,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr "Набір інструментів"
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -56140,61 +56344,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -56203,13 +56407,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -56218,11 +56422,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -56230,14 +56434,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -56245,14 +56449,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -56261,14 +56465,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -56278,7 +56482,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -56287,7 +56491,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -56296,7 +56500,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56327,7 +56531,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56337,7 +56541,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56345,14 +56549,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56360,21 +56564,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56383,7 +56587,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56393,7 +56597,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/vi.po b/weblate/vi.po
index cfefe23221..3c68e1f706 100644
--- a/weblate/vi.po
+++ b/weblate/vi.po
@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-10-05 02:39+0000\n"
 "Last-Translator: 01lifeleft <01lifeleft@gmail.com>\n"
 "Language-Team: Vietnamese <https://hosted.weblate.org/projects/godot-engine/"
@@ -77,13 +77,14 @@ msgstr ""
 "muốn, xin hãy cho chúng tôi biết."
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "Gửi một vấn đề (issue) hoặc kéo yêu cầu (pull request) trên `GitHub "
 "repository <https://github.com/godotengine/godot-docs/issues>`_, cùng giúp "
@@ -163,7 +164,6 @@ msgstr "Thông tin"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -182,6 +182,7 @@ msgstr "Thông tin"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -381,10 +382,11 @@ msgstr ""
 "mềm, phát triển các mô đun C ++ hoặc các phần mở rộng."
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1483,7 +1485,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1950,7 +1952,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -2025,13 +2027,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2275,8 +2277,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2300,7 +2302,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2374,7 +2376,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2388,7 +2390,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2728,6 +2730,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "Tín hiệu"
@@ -3198,7 +3201,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3324,7 +3327,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3533,7 +3536,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3631,7 +3634,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3659,7 +3662,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -4157,7 +4160,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4213,8 +4216,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4290,7 +4293,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4387,7 +4390,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4473,14 +4476,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4589,7 +4592,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4635,7 +4638,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4675,7 +4678,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4716,9 +4719,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4806,7 +4809,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4923,7 +4926,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4971,7 +4974,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -5113,7 +5116,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5221,7 +5224,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5245,7 +5248,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5572,9 +5575,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5604,8 +5608,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5645,8 +5650,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6548,7 +6553,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6617,9 +6622,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6636,12 +6641,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6664,8 +6669,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6841,10 +6847,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6923,16 +6929,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6943,7 +6949,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6985,7 +6991,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -7012,7 +7018,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -7161,7 +7167,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7176,7 +7182,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7254,7 +7260,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7281,7 +7287,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7418,9 +7424,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7489,16 +7495,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7515,14 +7521,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7553,16 +7559,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7624,7 +7630,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7654,7 +7660,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7800,7 +7806,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7830,7 +7836,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7862,7 +7868,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8297,9 +8303,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8609,7 +8615,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8689,7 +8695,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8806,12 +8812,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8863,7 +8869,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10299,7 +10305,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10679,7 +10685,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10758,7 +10764,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10784,7 +10790,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10995,9 +11001,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -11042,7 +11048,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -11088,7 +11094,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -11099,7 +11105,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11170,7 +11176,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11190,7 +11196,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19566,7 +19572,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr ""
 
@@ -22500,8 +22506,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22714,9 +22719,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24703,7 +24708,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25434,437 +25439,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27630,7 +27204,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27640,7 +27214,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42934,9 +42508,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42986,9 +42560,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -43042,46 +42616,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -43089,7 +42661,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -43098,7 +42670,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -43106,7 +42678,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -43116,7 +42688,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -43127,19 +42699,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -43147,13 +42719,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43161,7 +42733,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43170,7 +42742,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43184,7 +42756,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43193,7 +42765,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43201,10 +42773,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44169,6 +43741,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -47084,6 +46661,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51629,11 +51632,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51827,45 +51830,41 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -51875,29 +51874,30 @@ msgstr ""
 "Godot `Godot demo projects <https://github.com/godotengine/godot-demo-"
 "projects>`_."
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51905,131 +51905,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -52037,55 +52033,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -52096,22 +52092,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -52120,7 +52116,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -52128,11 +52124,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -52141,42 +52137,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52186,7 +52189,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52195,7 +52198,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52203,58 +52206,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54345,7 +54545,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54353,18 +54553,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54372,23 +54572,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54396,35 +54596,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54433,103 +54633,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54537,20 +54737,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54589,11 +54789,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54603,24 +54815,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54629,7 +54841,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54637,18 +54849,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54658,7 +54870,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54667,37 +54879,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54705,63 +54917,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54769,13 +54981,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54783,7 +54995,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54791,25 +55003,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54817,30 +55029,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54848,7 +55060,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54857,25 +55069,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54886,46 +55098,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54934,68 +55146,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -55003,7 +55215,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -55012,11 +55224,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -55024,114 +55236,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55198,37 +55410,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55236,61 +55448,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55310,18 +55522,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55329,11 +55541,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55341,37 +55553,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55432,27 +55644,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55460,24 +55672,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55485,29 +55684,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55515,35 +55714,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55551,40 +55750,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55592,131 +55791,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55736,29 +55935,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55769,17 +55968,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "Chạy"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55889,6 +56088,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55973,61 +56176,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -56036,13 +56239,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -56051,11 +56254,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -56063,14 +56266,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -56078,14 +56281,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -56094,14 +56297,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -56111,7 +56314,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -56120,7 +56323,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -56129,7 +56332,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56160,7 +56363,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56170,7 +56373,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56178,14 +56381,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56193,21 +56396,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56216,7 +56419,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56226,7 +56429,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
diff --git a/weblate/zh_CN.po b/weblate/zh_CN.po
index 4d3d9658f7..63a03f28d3 100644
--- a/weblate/zh_CN.po
+++ b/weblate/zh_CN.po
@@ -53,7 +53,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-12-04 22:23+0000\n"
 "Last-Translator: yzt <834950797@qq.com>\n"
 "Language-Team: Chinese (Simplified) <https://hosted.weblate.org/projects/"
@@ -112,13 +112,14 @@ msgstr ""
 "容，请告知我们以帮助我们更好地编写文档！"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "在 `GitHub仓库 <https://github.com/godotengine/godot-docs/issues>`_ 上提交问"
 "题或提交请求，帮助我们将 `文档 <https://hosted.weblate.org/engage/godot-"
@@ -188,7 +189,6 @@ msgstr "关于"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -207,6 +207,7 @@ msgstr "关于"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -385,10 +386,11 @@ msgstr ""
 "擎，开发C++组件和编辑器插件等信息。"
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1493,7 +1495,8 @@ msgid "It can be extended (to have more functions)."
 msgstr "能够被继承（以便拥有更多的功能）。"
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+#, fuzzy
+msgid "It can be added to another node as a child."
 msgstr "能够被加到其他节点作为子节点。"
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -2045,13 +2048,14 @@ msgstr ""
 "用其实例（或通过代码，或通过编辑器）来表达所属关系。"
 
 #: ../../docs/getting_started/step_by_step/instancing_continued.rst:43
+#, fuzzy
 msgid ""
 "A lot of time spent in programming games (or software in general) is on "
 "designing an architecture and fitting game components to that architecture. "
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 "开发游戏（或者是通用软件）的大部分时间被花费在设计结构并把游戏组件适配到这个"
@@ -2145,16 +2149,18 @@ msgstr ""
 "Godot官方支持四种（是的，四种！）语言，并且能够动态添加额外的语言！"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
+#, fuzzy
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 "这很好，主要在于提供了大量的灵活性，但也使得我们对语言的支持工作变得更加困"
 "难。"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
+#, fuzzy
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2433,9 +2439,10 @@ msgstr ""
 "脚本创建对话框会弹出。这个对话框允许你设置脚本语言、类名和其它相关选项。"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
+#, fuzzy
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr "在GDScript里，文件本身代表了类，所以类名一栏无法编辑。"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2461,9 +2468,10 @@ msgstr ""
 "本”图标或Inspector窗口中的Script属性来查看这个脚本："
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
+#, fuzzy
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 "要编辑脚本，选择上述按钮之一，这两个按钮都在上图中突出显示。这会把你带到脚本"
@@ -2554,11 +2562,12 @@ msgstr ""
 "及要触发的方法的名字。"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:205
+#, fuzzy
 msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 "左上部分显示了你的场景节点列表，其中触发节点的名称以红色突出显示。在这里选"
 "择“Panel”节点。当你选择一个节点时，底部的NodePath将自动更新为触发节点到所选节"
@@ -2576,9 +2585,10 @@ msgstr ""
 "之前生成这个函数。"
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
+#, fuzzy
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 "这就结束了关于如何使用可视界面的指南。然而这是一个脚本教程，所以为了学习，让"
@@ -2991,6 +3001,7 @@ msgstr "只有GDScript为每一个独立的脚本创建全局变量。"
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "信号"
@@ -3580,10 +3591,11 @@ msgstr ""
 "小的好时候："
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:198
+#, fuzzy
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 "现在我们可以使用``_process()``函数来定义玩家将会做什么。``_process()``在每一"
 "帧都会被调用，因此我们需要使用它来更新我们游戏中期望被经常改变的元素，这里我"
@@ -3741,10 +3753,11 @@ msgstr ""
 "上面代码中的布尔赋值是程序员的常用简写。 考虑此代码与上面缩短的布尔赋值："
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:372
+#, fuzzy
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 "再次运行场景并检查各方向的动画是否正确，当你确定移动正常工作的话，将下面一行"
 "代码加到``_ready()``中以便玩家在游戏开始时被隐藏："
@@ -3996,8 +4009,9 @@ msgid "See :ref:`doc_instancing` to learn more about instancing."
 msgstr "查阅 :ref:`doc_instancing`  来学习更多关于实例的知识。"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
+#, fuzzy
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 "现在, 将以下节点添加为 \"Main\" 的子级, 并按显示的名称命名它们 (值以秒为单"
@@ -4111,8 +4125,9 @@ msgid "Main script"
 msgstr "主脚本"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
+#, fuzzy
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 "在“Main”中添加一个脚本。在脚本的顶部，我们使用' export (PackedScene) ' '来允"
@@ -4148,8 +4163,9 @@ msgstr ""
 "时器’’）。“启动定时器”将启动其他两个定时器。‘记分计时器’将分数增加1。"
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
+#, fuzzy
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -4738,7 +4754,7 @@ msgstr "这是玩家的完整脚本，注释指出了我们做了哪些改变：
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr "导出模板"
@@ -4804,9 +4820,10 @@ msgstr ""
 "`.apk`或者 Windows 平台的 `.exe` 。"
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
+#, fuzzy
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 "在 \"Resources\" 和 ”Features\" 选项卡中，您可以自定义如何为每个平台导出游"
 "戏。我们可以先不考虑这些设置。"
@@ -4897,8 +4914,9 @@ msgstr ""
 "台工具”。这将安装Godot用来与设备通信的“adb”命令行工具。"
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
+#, fuzzy
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr "接下来，通过在系统的命令行上运行以下命令，创建一个调试密钥库:"
 
@@ -5003,9 +5021,10 @@ msgid ""
 msgstr "导出完成后，您将拥有一个包含以下文件的文件夹:"
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
+#, fuzzy
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -5114,9 +5133,10 @@ msgid "On top of that, you can **inherit** from any scene."
 msgstr "最重要的是，你可以从任何场景 **inherit** 。"
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
+#, fuzzy
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
@@ -5125,8 +5145,9 @@ msgstr ""
 "或者混合和匹配这两者来自由的设计它。"
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
+#, fuzzy
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -5265,9 +5286,10 @@ msgstr ""
 "件来替代。"
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
+#, fuzzy
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -5324,8 +5346,9 @@ msgstr ""
 "和场景，或者**创建插件和扩展编辑器**"
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
+#, fuzzy
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 "这导致了一个可靠和灵活的UI系统，因为它为编辑器本身提供了动力。使用“tool”关键"
@@ -5370,11 +5393,12 @@ msgid "Design interfaces with the Control nodes"
 msgstr "使用控制节点设计接口"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:6
+#, fuzzy
 msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -5420,11 +5444,12 @@ msgstr ""
 "<doc_ui_game_user_interface>中构建您的第一个游戏UI”。"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
+#, fuzzy
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 "在设计接口时只使用控制节点。它们具有独特的特性，使它们能够相互协作。其他节点"
@@ -5516,9 +5541,10 @@ msgid "TextureRect"
 msgstr "纹理结构"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
+#, fuzzy
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 "**纹理矩形**在UI中显示纹理或图像。它看起来类似于精灵节点，但它提供了多种缩放"
@@ -5658,12 +5684,13 @@ msgid "TextureProgress bar, two thirds filled"
 msgstr "文本进度条，三分之二填充"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:143
+#, fuzzy
 msgid ""
 "**Label** prints text to the screen. You'll find all its properties in the "
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 "**标签**打印文本到屏幕。您将在Label部分和Inspector中找到它的所有属性。在"
 "`text`属性中写入文本，如果希望它遵守文本框的大小，请选中Autowrap。如果"
@@ -5716,10 +5743,11 @@ msgstr ""
 "另一方面，你有布局菜单。它帮助您锚定、放置和调整UI元素在其父级中的大小。"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:174
+#, fuzzy
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -5890,11 +5918,12 @@ msgid "Arrange control nodes automatically with containers"
 msgstr "使用容器自动排列控制节点"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:275
+#, fuzzy
 msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 "容器自动排列所有子控件节点，包括行、列等中的其他容器。使用它们在接口周围或中"
 "心节点的边框中添加填充。所有内置容器在编辑器中更新，以便您可以立即看到效果。"
@@ -6023,9 +6052,10 @@ msgid "A GridContainer with 2 columns. It sizes each column automatically."
 msgstr "一个有两列的GridContainer（网格容器）。它会自动调整每个列的大小。"
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
+#, fuzzy
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 "Godot的UI系统很复杂，还有很多东西可以提供。要了解如何设计更高级的界面，请访"
@@ -6051,8 +6081,9 @@ msgid "A game UI with a health bar, energy bar, bomb and money counters"
 msgstr "一个带有健康条、能量条、炸弹和金钱计数器的游戏UI"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
+#, fuzzy
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -6432,13 +6463,15 @@ msgid "There's no space between the logo and the other UI elements"
 msgstr "logo和其他UI元素之间没有空间"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:219
+#, fuzzy
 msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 "为了使右边的字符居中，我们将使用`CenterContainer`。添加一个`CenterContainer`"
 "节点作为`HBoxContainer`的子节点。然后在检查器中，向下滚动到`Size Flags（大小"
@@ -6473,13 +6506,15 @@ msgid ""
 msgstr "将新容器放在其他两个节点之间，以保持UI的布局"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:244
+#, fuzzy
 msgid ""
 "Now we grouped the menu options together, we can tell their container to "
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 "现在我们将菜单选项组合在一起，我们可以告诉它们的容器扩展到尽可能多的垂直空"
 "间。选择`MenuOptions`节点。在检查器中，向下滚动到`Size Flags（大小标志）`类"
@@ -6530,9 +6565,10 @@ msgstr ""
 "教程中，您将创建一个带有栏和物品计数器的游戏用户界面。"
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
+#, fuzzy
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -7672,8 +7708,9 @@ msgid "Intro"
 msgstr "简介"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
+#, fuzzy
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr "在本教程中，你将连接一个字符到生命条，并播放健康损失。"
 
@@ -7746,14 +7783,15 @@ msgid "To do this, we will use **signals**."
 msgstr "为此，我们将使用**信号**。"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:49
+#, fuzzy
 msgid ""
 "Signals are Godot's version of the Observer pattern. They allow us to send "
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 "信号是Godot观察者模式的版本。他们允许我们发出一些信息。其他节点可以连接到"
@@ -7777,13 +7815,14 @@ msgstr ""
 "*start*和*end*。"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
+#, fuzzy
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 "加载Godot中的`start`项目。在`FileSystem`dock中双击LevelMockup.tscn打开它。这"
 "是一个RPG游戏的模型，两个角色面对面。粉色的敌人定期攻击并破坏绿色的正方形，直"
@@ -7813,9 +7852,11 @@ msgid "The scene tree, with the GUI scene set to display its children"
 msgstr "场景树，用GUI场景设置来显示它的子对象"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
+#, fuzzy
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 "GUI场景封装了所有的游戏用户界面。它附带了一个基本的脚本，我们可以在其中获得到"
 "场景中存在的节点的路径："
@@ -8043,11 +8084,12 @@ msgstr ""
 "在网上免费获得。"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
+#, fuzzy
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 "考虑到这一点，让我们将`GUI`连接到`Playe`。点击场景dock中的`Player`节点来选择"
 "它。转到检查器，单击Node选项卡。这是连接节点侦听所选节点的地方。"
@@ -8138,20 +8180,22 @@ msgid "Godot writes the callback method for you and takes you to it"
 msgstr "Godot为你编写回调方法并将你带到它"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
+#, fuzzy
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 "在函数名后面的参数中，添加一个`player_health`参数。当玩家发出`health_changed`"
 "信号时，它会将当前的`health`发送到旁边。您的代码应该如下所示："
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
+#, fuzzy
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 "引擎不会将PascalCase转换成snake_case，对于C#示例，我们将使用PascalCase来表示"
 "方法名，而camelCase用于方法参数，这些参数遵循 `官方的C#命名约定。 <https://"
@@ -8165,8 +8209,9 @@ msgid ""
 msgstr "在Player.gd。当玩家发出health\\_changed信号时，它也会发送其health值"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
+#, fuzzy
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 "在`_on_Player_health_changed`中，我们调用第二个函数`update_health`，并将"
@@ -8213,9 +8258,10 @@ msgid "set the ``TextureProgress``'s ``value`` to ``new_value``"
 msgstr "将`TextureProgress`的`value`设置为`new_value`"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
+#, fuzzy
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr "`str`是一个内置函数，可以将任何值转换为文本"
 
@@ -8240,11 +8286,12 @@ msgid "Animate the loss of life with the Tween node"
 msgstr "用渐变节点动画生命的损失"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:367
+#, fuzzy
 msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -8431,7 +8478,8 @@ msgstr ""
 "乱。考虑到游戏的风格，生命条以一种更加起伏不定的方式进行动画是很好的。"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+#, fuzzy
+msgid "The animation is smooth, but the number is broken"
 msgstr "动画很流畅，但是数字被打破了"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -8449,7 +8497,8 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr "再次尝试游戏，看看一个不错的方块动画。"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+#, fuzzy
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr "通过完成animated\\_health，我们达到了一石二鸟的效果"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -8542,10 +8591,11 @@ msgstr ""
 "见性，给它分配一个着色器，然后用一个带有`modulate`的颜色来修改它。"
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:611
+#, fuzzy
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 "`modulate`具有`Color`值，有4个通道：红色、绿色、蓝色和alpha。如果我们使前三个"
 "通道中的任何一个都变暗，它就会使界面变暗。如果我们降低alpha通道，我们的界面就"
@@ -8580,8 +8630,9 @@ msgid ""
 msgstr "然后我们必须再次调用`Tween`节点的`interpolate_property`方法："
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
+#, fuzzy
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -8738,10 +8789,11 @@ msgstr ""
 "`intro`。"
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
+#, fuzzy
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 "现在我们有一个动画，属性编辑器进入`animation editing 动画编辑`模式。在这种模"
 "式下，属性编辑器的每个属性旁边都会出现一个键图标。在Godot中，对象的任何属性都"
@@ -8814,10 +8866,11 @@ msgid "Nodes and resources"
 msgstr "节点和资源"
 
 #: ../../docs/getting_started/step_by_step/resources.rst:9
+#, fuzzy
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 "在本教程之前, 我们重点介绍了Godot中的 :ref:`Node <class_Node>` 类： 因为它是"
@@ -8825,11 +8878,12 @@ msgstr ""
 "同样重要:ref:`Resource <class_Resource>`。"
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
+#, fuzzy
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 "*节点*给你提供了功能：它们绘制精灵，3D模型，模拟物理，安排用户界面等。*资源*"
 "是*数据容器*。它们不会自己作任何事情，而节点会使用资源包含的数据。"
@@ -8850,19 +8904,21 @@ msgstr ""
 "<class_Font>`, :ref:`Translation <class_Translation>`。"
 
 #: ../../docs/getting_started/step_by_step/resources.rst:26
+#, fuzzy
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 "当引擎从磁盘加载资源时, **它只加载一次**。如果该资源的副本已在内存中, 则尝试"
 "再次加载该资源将每次返回相同的副本。由于资源只包含数据, 因此无需复制它们。"
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
+#, fuzzy
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -8897,17 +8953,19 @@ msgstr ""
 "<class_Texture>`："
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
+#, fuzzy
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr "单击资源预览可以查看和编辑资源属性。"
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
+#, fuzzy
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 "Path属性告诉我们资源来自何处。在这里，它来自一个叫``robi.png``的PNG图像。当资"
 "源来自这样的文件时，它属于外部资源。如果您去掉这个路径或此路径为空，则它将成"
@@ -8981,11 +9039,12 @@ msgstr ""
 "以将其添加为任何其他节点的子节点。"
 
 #: ../../docs/getting_started/step_by_step/resources.rst:137
+#, fuzzy
 msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 "这种方法有几个优点。由于:ref:`PackedScene.instance() "
@@ -9024,8 +9083,9 @@ msgstr ""
 "类型的引用计数内存管理。"
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
+#, fuzzy
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -9200,8 +9260,9 @@ msgstr ""
 "加到检查器中。"
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
+#, fuzzy
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 "CurveTables 是相同的事情, 除了映射到浮点值的数组或:ref:`Curve "
@@ -9235,11 +9296,12 @@ msgid "File system"
 msgstr "文件系统"
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:9
+#, fuzzy
 msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 "文件系统也是游戏引擎开发的热门话题之一。文件系统掌管着资源(assets)的存取。一"
 "个好的文件系统能让团队中的成员们共同编辑相同的源文件和资源。"
@@ -9278,10 +9340,11 @@ msgstr ""
 "源(sub-resources)，那么所有的子资源都会和它一起打包在一个文件当中。"
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:30
+#, fuzzy
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 "总的来讲，Godot的文件系统并未使用元数据文件，理由很简单，现在的各种资产管理系"
@@ -9812,11 +9875,12 @@ msgstr ""
 "载\" 选项卡。"
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
+#, fuzzy
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 "在这里, 您可以添加任意数量的场景或脚本。列表中的每个条目都需要一个名称, 该名"
 "称分配给节点的 ``name`` 属性。可以使用向上箭头键操作添加到全局场景树中的条目"
@@ -10158,12 +10222,13 @@ msgid ""
 msgstr "请注意，Godot编辑器允许您任意将各个面板停靠在场景编辑器的一侧。"
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:57
+#, fuzzy
 msgid ""
 "While both editors may seem similar, there are many differences below the "
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 "虽然这两个编辑器看上去相同，但是在外表之下有着许多的不同。两者都允许你使用文"
 "件系统来组织项目，但是Godot的方法更简单，只需要一个非常小的文本格式文件，而不"
@@ -10267,8 +10332,9 @@ msgstr ""
 "本将它们链接在一起。"
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
+#, fuzzy
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -10413,13 +10479,14 @@ msgstr ""
 "对象”的节点，但它们为子节点提供了自己本身的功能：这就是继承。"
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
+#, fuzzy
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 "其次，它允许抽出场景的一个子树使其成为它自己的一个场景，这回答了第二个和第三"
 "个问题：即使场景树变得太深，它也可以拆分成更小的子树。这也提供了有着可重用性"
@@ -10483,9 +10550,10 @@ msgstr ""
 "的预制体的每个实例都有其自己的存在，但它们都具有与预制体所定义的相同的属性。"
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
+#, fuzzy
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -12060,10 +12128,11 @@ msgstr ""
 "中一样，从尾部开始计数。"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:489
+#, fuzzy
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -12500,8 +12569,9 @@ msgid "Remove ``case``"
 msgstr "删除 ``case``"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
+#, fuzzy
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 "删除任何``break``。如果默认情况下不想``break``，可以使用``continue``作为故障"
@@ -12585,9 +12655,10 @@ msgid ""
 msgstr "匹配一个数组。数组模式的每个元素本身就是一个模式，因此可以嵌套它们。"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
+#, fuzzy
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr "首先测试数组的长度，它必须与模式相同大小，否则模式不匹配。"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -12611,9 +12682,10 @@ msgid ""
 msgstr "工作方式与数组模式相同。每个键必须是一个常量模式。"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
+#, fuzzy
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr "首先测试字典的大小，它必须与模式的大小相同，否则模式不匹配。"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -12855,11 +12927,12 @@ msgstr ""
 "下面)。"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
+#, fuzzy
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 "导出成员变量的基本好处之一是使它们在编辑器中可见并可编辑。通过这种方式，艺术"
 "家和游戏设计师可以修改影响程序运行的值。为此，提供了一种特殊的导出语法。"
@@ -12911,8 +12984,9 @@ msgid "Exporting arrays"
 msgstr "导出数组"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
+#, fuzzy
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -12969,8 +13043,9 @@ msgstr ""
 "在工具脚本或插件中， Get/Setters可将变量导出到编辑器，这可以用于验证输入。"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
+#, fuzzy
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr "如上所述， *本地* 访问 *不* 需要触发setter和getter。 这里有个说明："
 
@@ -12979,9 +13054,10 @@ msgid "Tool mode"
 msgstr "工具模式"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
+#, fuzzy
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -13061,13 +13137,14 @@ msgid "Coroutines with yield"
 msgstr "有yield的协同程序"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1520
+#, fuzzy
 msgid ""
 "GDScript offers support for `coroutines <https://en.wikipedia.org/wiki/"
 "Coroutine>`_ via the ``yield`` built-in function. Calling ``yield()`` will "
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 "GDScript通过“yield”内置函数支持“coroutines <https://en.wikipedia.org/wiki/"
 "Coroutine>”_。调用' ' yield() ' '将立即从当前函数返回，当前函数的冻结状态与返"
@@ -13089,9 +13166,10 @@ msgid "Coroutines & signals"
 msgstr "协程&信号"
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
+#, fuzzy
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 "使用 ``yield`` 的真正强度是在与信号结合时。 ``yield`` 可以接受两个参数，一个"
@@ -22766,7 +22844,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr "让我们再跑一次！ 这次，旋转显示正常！"
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "工具"
 
@@ -26256,10 +26334,10 @@ msgstr ""
 "人称游戏中的角色）。"
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
+#, fuzzy
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr "始终确保根据场景需要设置阴影*最大距离*。 距离越近，阴影的质量越高。"
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -26498,10 +26576,11 @@ msgid ""
 msgstr "如果上述情况均未发生，则不执行任何操作，阴影保持不变。"
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
+#, fuzzy
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 "此分配策略适用于大多数游戏，但在某些情况下您可能会使用单独的游戏（例如，自上"
 "而下的游戏，其中所有灯光大小相同，四边形可能具有相同的细分）。"
@@ -28831,7 +28910,8 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ":ref:`CSGMesh <class_CSGMesh>`"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+#, fuzzy
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ":ref:`CSGCombiner <class_CSGcombiner>'"
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -29674,548 +29754,6 @@ msgstr ""
 "在根节点下创建一个新的Spatial节点，并将其重命名为“target”。 然后修改"
 "``_ready（）``函数看起来像这样："
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr "使用着色器的顶点偏移"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-"本教程将教您如何在着色器中替换：ref：`Plane Mesh <class_PlaneMesh>`的顶点。 "
-"顶点位移可用于各种效果，但最常见的是它用作将平面转变为简单地形的快速方法。 通"
-"常这是使用高度图完成的，但为了保持所有内容的自包含，在本教程中我们将使用着色"
-"器中的噪声。 在本教程结束时，我们将看到一个变形的平面，看起来像一个完整的动态"
-"光照的微型地形。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr "通过阅读本教程，您应该基本了解："
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr "如何创建和细分：ref：`Plane Mesh <class_PlaneMesh>`"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr "如何创建和分配材料到：ref：`Mesh <class_MeshInstance>`"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-"如何写一个：ref：`Shader <class_Shader>`替换a：ref：`Mesh "
-"<class_MeshInstance>的顶点"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-"如何将值（Uniforms）传递到：ref：`Shader <class_Shader>`以实时更新：ref："
-"`Mesh <class_MeshInstance>`"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr "如何从高度函数近似法线"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr "如何使用自定义材料的灯光"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr "平面网格"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-"首先，在场景中添加一个：ref：`Spatial <class_Spatial>`节点作为根。 接下来，添"
-"加：ref：`MeshInstance <class_MeshInstance>`作为孩子。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-"选择新创建的：ref：`MeshInstance <class_MeshInstance>`。 然后单击Inspector"
-"中：ref：`Mesh <class_MeshInstance>`旁边的“null”按钮。 这将显示一个列表："
-"ref：`PrimitiveMeshes <class_PrimitiveMesh>`。 选择“New PlaneMesh”。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-"该按钮将变为平面的小图像。 单击它进入Inspector，进入：ref：`Plane Mesh "
-"<class_MeshInstance>`。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-"然后，在视口中，单击左上角，显示[透视]。 将出现一个菜单。 菜单中间是如何显示"
-"场景的选项。 选择“显示线框”。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr "这将允许您查看构成平面的三角形。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr "现在将``Subdivide Width``和``Subdivide Height``设置为``32``。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-"您可以看到现在有更多三角形：ref：`Mesh <class_MeshInstance>`。 这将为我们提供"
-"更多顶点，从而允许我们添加更多细节。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr "着色器魔术"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-"现在我们有了一个：ref：`Plane Mesh <class_MeshInstance>`来绘制让我们设置将变"
-"形的材质：ref：`Mesh <class_MeshInstance>`。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-"单击下面的材料：ref：`Plane Mesh <class_MeshInstance>`菜单并创建一个新的："
-"ref：`ShaderMaterial <class_ShaderMaterial>`。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr "然后单击created：ref：`ShaderMaterial <class_ShaderMaterial>`。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr "然后单击“着色器”旁边的并创建一个新的：ref：`Shader <class_Shader>`。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-"单击新创建的：ref：`Shader <class_Shader>`。 你现在应该看看Godot的Shader编辑"
-"器。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-"注意它是如何抛出错误的？ 这是因为着色器编辑器会自动重新加载着色器。 Godot着色"
-"器需要的第一件事就是声明它们是什么类型的着色器。 因此，我们将变量"
-"``shader_type``设置为``spatial``。 我们要添加的另一件事是``render_mode``，我"
-"们将它设置为``unshaded``。 这意味着Godot不会在此对象上运行灯光着色器。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-"这应该删除错误，你的：ref：`Mesh <class_MeshInstance>`应该变成白色。 如果你要"
-"注释掉``render_mode``，飞机会显得很蓝，因为它会拾取天空的颜色。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-"接下来我们将定义一个顶点着色器。 顶点着色器确定最终场景中出现的地址：ref："
-"`Mesh <class_MeshInstance>`的顶点。 我们将使用它来偏移每个顶点的高度，并使我"
-"们的平面看起来像一个小地形。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr "我们像这样定义顶点着色器："
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-"在``vertex``函数中没有任何内容，Godot将使用其默认的顶点着色器。 我们可以通过"
-"添加一行来轻松开始进行更改："
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr "添加此行您应该得到如下图像。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-"好吧，让我们打开它。 ``VERTEX``的``y``值正在增加。 我们传递``VERTEX``的``x``"
-"和``z``组件作为``cos``和``sin``的参数，这给了我们一个横跨``x的波浪外观 ``和"
-"``z``轴。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-"我们想要实现的是小山丘的外观，毕竟``cos``和``sin``看起来有点像山丘。 我们通过"
-"缩放“cos``和``sin``函数的输入来实现。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-"这看起来更好，但它仍然太尖刻。 这是因为``cos``和``sin``在``-1``和````之间输出"
-"值，所以输出的范围太高了。 我们通过将结果乘以“0.5”来纠正这个问题以减小尺寸。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-"现在看起来更加丘陵了。 但是``cos``和``sin``很无聊。 让我们进入更有趣的事情。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr "噪声"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-"噪声是一种非常流行的程序生成工具。 可以认为它类似于余弦函数，除了噪音外，每个"
-"山都有不同的高度。 本教程不需要了解噪声。 简单地复制和粘贴下面的代码没有任何"
-"问题。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr "我们用来生成噪波的第一个函数是“hash”函数。它给出了每个山顶的随机高度。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-"您将在整个互联网上找到类似的功能。 它被巧妙地称为“单线程哈希函数”。 它适用于"
-"简单的噪音，但也有许多更好的替代方案。 对于本教程，它将正常工作。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-"接下来我们定义“noise”函数。它平滑地插入到随机高度之间。同样，如果这段代码看起"
-"来很吓人，不要担心，只需复制粘贴并且跟着教程继续学习。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-"最后，为了添加细节，我们使用分形布朗运动或FBM来组合连续的噪声层。 除了FBM噪声"
-"之外，可怕的名称只会增加噪声层，增加频率并降低幅度。 为了实现它，我们运行for"
-"循环，我们增加每个级别的频率，减小幅度，并计算新的噪声层。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr "我们现在可以使用这个噪声函数代替上一节中的``cos``和``sin``。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-"有了噪音功能，我们已经有了一些看起来很酷的东西。 有很多细节，有点像丘陵或山"
-"区。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr "片段着色器"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-"顶点着色器和片段着色器之间的区别在于顶点着色器每个顶点运行并设置诸"
-"如“VERTEX”（位置）和“正常”的属性，而片段着色器按像素运行，最重要的是， 设置："
-"ref：`Mesh <class_MeshInstance>`的``ALBEDO``颜色。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-"现在让我们看一下：ref：`Mesh <class_MeshInstance>`用常规着色器而不是线框。 将"
-"视口设置回“显示正常”。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-"：ref：`Mesh <class_MeshInstance>`看起来是完全白色的，因为片段着色器将每个像"
-"素着色为白色，但如果每个像素都是白色，我们就会丢失详细信息：ref：`Mesh "
-"<class_MeshInstance>`。 因此，让我们根据顶点着色器中计算的高度为每个像素着"
-"色。 我们通过在顶点着色器中设置``COLOR``变量来实现。 并通过将片段着色器中"
-"的“ALBEDO”设置为计算的“COLOR”变量。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-"通过这个更改，我们可以看到：ref：`Mesh <class_MeshInstance>`的细节，即使没有"
-"显示：ref：`Mesh <class_MeshInstance>`的线框。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr "制服"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-"统一变量允许您将数据从游戏传递到着色器。 它们对于控制着色器效果非常有用。 制"
-"服几乎可以是着色器中可以使用的任何数据类型。 要使用制服，请使用关键字"
-"``uniform``在：ref：`Shader <class_Shader>`中声明它。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr "让我们制作一个改变地形高度的制服。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-"Godot允许你用值初始化一个制服，这里``height_scale``设置为``0.5``。 您可以通过"
-"在与着色器对应的材质上调用函数``set_shader_param``来设置gdscript中的制服。 从"
-"gdscript传递的值优先于用于在着色器中初始化它的值。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-"请记住，传递给``set_shader_param``的字符串必须与：ref：`Shader "
-"<class_Shader>`中的统一变量的名称匹配。 您可以在：ref：`Shader "
-"<class_Shader>`中的任何位置使用统一变量。 在这里，我们将使用它来设置高度值，"
-"而不是任意乘以“0.5”。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-"地形应该看起来完全一样，但现在我们可以轻松控制高度。 这里是``height_scale``设"
-"置为``1``的相同地形："
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr "在这里，``height_scale``设置为``0.2``："
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-"使用制服我们甚至可以改变每帧的值来设置地形的高度。 结合：ref：`Tweens "
-"<class_Tween>`这对简单的动画特别有用。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr "与光交互"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-"作为本教程的最后一部分，我们尝试设置地形以与光交互。 首先，我们将向场景中添"
-"加：ref：`OmniLight <class_OmniLight>`。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-"您应该注意到没有任何变化，这是因为我们在本教程的开头将``render_mode``设置为"
-"``unshaded``，让我们删除它。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-"它现在看起来稍微好一点，你可以看到影响地形的光线，并且它因天空而变成了蓝色。 "
-"问题是光线正在影响地形，好像它是一个平面。 这是因为灯光着色器使用：ref："
-"`Mesh <class_MeshInstance>`的法线来计算光。 法线存储在：ref：`Mesh "
-"<class_MeshInstance>`中，但是我们正在改变着色器中的：ref：`Mesh "
-"<class_MeshInstance>`的形状，因此法线不再正确。 要解决此问题，我们需要重新计"
-"算着色器中的法线。 Godot让我们很容易，我们所要做的就是计算新法线并在顶点着色"
-"器中将``NORMAL``设置为该值。 通过``NORMAL``设置，戈多将为我们完成所有困难的灯"
-"光计算。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-"为了从噪声中计算法线，我们将使用一种称为“中心差异”的技术。 这很常用，特别是在"
-"像shadertoy这样的地方，用于计算着色器中的法线。 我们要做的是计算“x”和“z”方向"
-"顶点周围四个点的噪声，然后计算顶点的斜率。 毕竟法线只是噪音斜率的指标。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr "我们在顶点着色器中用一条线计算法线。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-"变量``e``只是更容易从``VERTEX``中添加和减去正确的值。 将``e``设置为较低的数字"
-"将增加法线的细节水平。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr "使用“NORMAL”计算地形现在看起来像："
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-"这看起来仍然不是我们想要的。 这里的问题是噪声变化比顶点变化得快。 因此，当我"
-"们计算“VERTEX”点时的法线时，它与我们在final中看到的不一致：ref：`Mesh "
-"<class_MeshInstance>`。 为了解决这个问题，我们添加了更多顶点。 下面的图像是"
-"用：ref：`Mesh <class_MeshInstance>`，``subdivision``设置为``100``。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr "现在我们可以拖动灯光，灯光会自动更新。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-"如果你缩小相机，你可以看到：ref：`Mesh <class_MeshInstance>`现在看起来像一个"
-"小地形。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-"这就是本教程的一切。 希望您了解戈多的顶点着色器的基础知识。 作为进一步的练习"
-"尝试从gdscript更改``height_scale``，尝试使用不同的：ref：`Primitive Meshes "
-"<class_PrimitiveMesh>`，并尝试使用自己的函数来计算``height``。"
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-"有关如何在Godot中使用着色器的更多信息，请查看：ref：`doc_shading_language`页"
-"面。"
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr "FPS教程"
@@ -32356,8 +31894,9 @@ msgstr ""
 "<class_Area>`来检查我们是否与某些东西相撞"
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
+#, fuzzy
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -32371,8 +31910,9 @@ msgstr ""
 "个：ref：`RigidBody <class_RigidBody>`节点，包括其他子弹，将受到影响。"
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
+#, fuzzy
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 "另一个原因很简单，因为用以下方法检测碰撞更容易：ref：`Area <class_Area>`！"
@@ -50266,10 +49806,11 @@ msgstr ""
 "`ColorRect <class_ColorRect>`。"
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
+#, fuzzy
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 "我们假设您熟悉本教程的着色基础知识。 即使你不是，所有的代码仍然会提供，所以你"
 "应该没有问题。"
@@ -50326,13 +49867,14 @@ msgid ""
 msgstr "现在，您的球体应使用我们渲染到视口的颜色进行着色"
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:94
+#, fuzzy
 msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 "注意形成纹理的地方形成的丑陋缝隙？ 这是因为我们正在选择基于UV坐标的颜色，并且"
 "UV坐标不会环绕纹理。 这是2D地图投影中的经典问题。 Gamedevs通常有一个他们希望"
@@ -50403,30 +49945,33 @@ msgid "And if we use ``unit`` as an output ``COLOR`` value we get."
 msgstr "如果我们使用``unit``作为输出``COLOR``值，我们得到。"
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:147
+#, fuzzy
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 "现在我们可以计算球体表面的3D位置，我们可以使用3D噪声来制作行星。 我们将直接从"
 "`Shadertoy <https://www.shadertoy.com/view/4dffRH>`_使用此噪音功能："
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
+#, fuzzy
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr "归功于最初的作者Inigo Quilez。 它与``MIT``许可证一起发布。"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
+#, fuzzy
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr "现在使用``noised``，将以下内容添加到``fragment``函数中："
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr "为了突出显示纹理，我们将材质设置为无阴影。"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
@@ -50435,24 +49980,24 @@ msgstr ""
 "你现在可以看到噪音确实在球体周围无缝包裹。 虽然这看起来不像你所承诺的星球。 "
 "所以让我们进入更丰富多彩的东西。"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr "着色这个星球"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
+#, fuzzy
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 "现在要让行星变色。 有很多方法可以做到这一点，如果你看看`Shadertoy <https://"
 "www.shadertoy.com>`_你将找到各种方法将颜色映射到程序行星地形。 现在我们将坚持"
 "水与陆之间的简单梯度。"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
+#, fuzzy
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -50464,7 +50009,7 @@ msgstr ""
 "常称为“lerp”。 虽然``lerp``通常用于将两个浮点数混合在一起，但``mix``可以取任"
 "何值，无论它是浮点数还是矢量类型。"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -50477,7 +50022,7 @@ msgstr ""
 "之间平滑变化。 所以我们把它映射到``mix``期望的``0-1``范围。 现在您可以看到颜"
 "色在蓝色和红色之间变化。"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -50488,7 +50033,7 @@ msgstr ""
 "做到这一点，我们将最后一个术语改为“smoothstep（-0.1,0.0，n.x）``。 因此整条线"
 "变为："
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -50502,7 +50047,7 @@ msgstr ""
 "``0``` 第三个数字在第一个和第二个之间。 因此，当``nx``小于`-0.1``时，"
 "``smoothstep``返回``0``，并且每当``nx``高于``0时'它返回``1```。"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -50517,19 +50062,19 @@ msgstr ""
 "们使用一层来构建大陆的整体blobby结构。 然后另一层分裂边缘，然后是另一层，依此"
 "类推。 我们要做的是用四行着色器代码计算``n``而不是一行。 ``n``成为："
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr "现在这个星球看起来像："
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr "随着阴影重新开启，它看起来像："
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr "制作海洋"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -50540,14 +50085,14 @@ msgstr ""
 "此，我们希望海洋比陆地更加闪耀。 我们可以通过将第四个值传递到输出``COLOR``的"
 "``alpha``通道并将其用作粗糙度图来实现。"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 "这一行返回水的“0.3”和土地的“1.0”。 这意味着土地将非常粗糙，而水将非常平坦。"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -50558,7 +50103,7 @@ msgstr ""
 "为``1``。 原因是水很好地反射光，但不是金属。 这些值在物理上并不准确，但它们对"
 "于此演示来说已经足够好了。"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -50571,7 +50116,7 @@ msgstr ""
 "<class_Viewport>`。 最后将``Texture Channel``设置为``Alpha``。 这指示渲染器使"
 "用输出``COLOR``的``alpha``通道作为``Roughness``值。"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -50592,7 +50137,7 @@ msgstr ""
 "`Viewport <class_Viewport>`并将“Transparent Bg”设置为on。 由于我们现在将一个"
 "透明对象渲染到另一个上面，我们想要启用``blend_premul_alpha``："
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -50604,7 +50149,7 @@ msgstr ""
 "透明颜色混合在另一个上面时，即使背景的“alpha``为”0“（就像在这种情况下一样），"
 "你最终会出现奇怪的颜色流失问题。 设置``blend_premul_alpha``修复了这个问题。"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -50615,10 +50160,11 @@ msgstr ""
 "请在场景中添加：ref：`OmniLight <class_OmniLight>`，这样您就可以移动它并查看"
 "反射对海洋的影响。"
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
+#, fuzzy
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr "你有它。 使用：ref：`Viewport <class_Viewport>`生成的简单程序行星。"
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -51672,6 +51218,11 @@ msgid ""
 "default"
 msgstr "该值以透视正确的方式进行插值。 这是默认值"
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr "制服"
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -54748,6 +54299,543 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr "Shaders使用相同的坐标系：ref：`GLSL <glsl_coordinates>`。"
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr "使用着色器的顶点偏移"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+"本教程将教您如何在着色器中替换：ref：`Plane Mesh <class_PlaneMesh>`的顶点。 "
+"顶点位移可用于各种效果，但最常见的是它用作将平面转变为简单地形的快速方法。 通"
+"常这是使用高度图完成的，但为了保持所有内容的自包含，在本教程中我们将使用着色"
+"器中的噪声。 在本教程结束时，我们将看到一个变形的平面，看起来像一个完整的动态"
+"光照的微型地形。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr "通过阅读本教程，您应该基本了解："
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr "如何创建和细分：ref：`Plane Mesh <class_PlaneMesh>`"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr "如何创建和分配材料到：ref：`Mesh <class_MeshInstance>`"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+"如何写一个：ref：`Shader <class_Shader>`替换a：ref：`Mesh "
+"<class_MeshInstance>的顶点"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+"如何将值（Uniforms）传递到：ref：`Shader <class_Shader>`以实时更新：ref："
+"`Mesh <class_MeshInstance>`"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr "如何从高度函数近似法线"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr "如何使用自定义材料的灯光"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr "平面网格"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+"首先，在场景中添加一个：ref：`Spatial <class_Spatial>`节点作为根。 接下来，添"
+"加：ref：`MeshInstance <class_MeshInstance>`作为孩子。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+"选择新创建的：ref：`MeshInstance <class_MeshInstance>`。 然后单击Inspector"
+"中：ref：`Mesh <class_MeshInstance>`旁边的“null”按钮。 这将显示一个列表："
+"ref：`PrimitiveMeshes <class_PrimitiveMesh>`。 选择“New PlaneMesh”。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+"该按钮将变为平面的小图像。 单击它进入Inspector，进入：ref：`Plane Mesh "
+"<class_MeshInstance>`。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+"然后，在视口中，单击左上角，显示[透视]。 将出现一个菜单。 菜单中间是如何显示"
+"场景的选项。 选择“显示线框”。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr "这将允许您查看构成平面的三角形。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr "现在将``Subdivide Width``和``Subdivide Height``设置为``32``。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+"您可以看到现在有更多三角形：ref：`Mesh <class_MeshInstance>`。 这将为我们提供"
+"更多顶点，从而允许我们添加更多细节。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr "着色器魔术"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+"现在我们有了一个：ref：`Plane Mesh <class_MeshInstance>`来绘制让我们设置将变"
+"形的材质：ref：`Mesh <class_MeshInstance>`。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+"单击下面的材料：ref：`Plane Mesh <class_MeshInstance>`菜单并创建一个新的："
+"ref：`ShaderMaterial <class_ShaderMaterial>`。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr "然后单击created：ref：`ShaderMaterial <class_ShaderMaterial>`。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr "然后单击“着色器”旁边的并创建一个新的：ref：`Shader <class_Shader>`。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+"单击新创建的：ref：`Shader <class_Shader>`。 你现在应该看看Godot的Shader编辑"
+"器。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+"注意它是如何抛出错误的？ 这是因为着色器编辑器会自动重新加载着色器。 Godot着色"
+"器需要的第一件事就是声明它们是什么类型的着色器。 因此，我们将变量"
+"``shader_type``设置为``spatial``。 我们要添加的另一件事是``render_mode``，我"
+"们将它设置为``unshaded``。 这意味着Godot不会在此对象上运行灯光着色器。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+"这应该删除错误，你的：ref：`Mesh <class_MeshInstance>`应该变成白色。 如果你要"
+"注释掉``render_mode``，飞机会显得很蓝，因为它会拾取天空的颜色。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+"接下来我们将定义一个顶点着色器。 顶点着色器确定最终场景中出现的地址：ref："
+"`Mesh <class_MeshInstance>`的顶点。 我们将使用它来偏移每个顶点的高度，并使我"
+"们的平面看起来像一个小地形。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr "我们像这样定义顶点着色器："
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+"在``vertex``函数中没有任何内容，Godot将使用其默认的顶点着色器。 我们可以通过"
+"添加一行来轻松开始进行更改："
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr "添加此行您应该得到如下图像。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+"好吧，让我们打开它。 ``VERTEX``的``y``值正在增加。 我们传递``VERTEX``的``x``"
+"和``z``组件作为``cos``和``sin``的参数，这给了我们一个横跨``x的波浪外观 ``和"
+"``z``轴。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+"我们想要实现的是小山丘的外观，毕竟``cos``和``sin``看起来有点像山丘。 我们通过"
+"缩放“cos``和``sin``函数的输入来实现。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+"这看起来更好，但它仍然太尖刻。 这是因为``cos``和``sin``在``-1``和````之间输出"
+"值，所以输出的范围太高了。 我们通过将结果乘以“0.5”来纠正这个问题以减小尺寸。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+"现在看起来更加丘陵了。 但是``cos``和``sin``很无聊。 让我们进入更有趣的事情。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr "噪声"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+"噪声是一种非常流行的程序生成工具。 可以认为它类似于余弦函数，除了噪音外，每个"
+"山都有不同的高度。 本教程不需要了解噪声。 简单地复制和粘贴下面的代码没有任何"
+"问题。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr "我们用来生成噪波的第一个函数是“hash”函数。它给出了每个山顶的随机高度。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+"您将在整个互联网上找到类似的功能。 它被巧妙地称为“单线程哈希函数”。 它适用于"
+"简单的噪音，但也有许多更好的替代方案。 对于本教程，它将正常工作。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+"接下来我们定义“noise”函数。它平滑地插入到随机高度之间。同样，如果这段代码看起"
+"来很吓人，不要担心，只需复制粘贴并且跟着教程继续学习。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+"最后，为了添加细节，我们使用分形布朗运动或FBM来组合连续的噪声层。 除了FBM噪声"
+"之外，可怕的名称只会增加噪声层，增加频率并降低幅度。 为了实现它，我们运行for"
+"循环，我们增加每个级别的频率，减小幅度，并计算新的噪声层。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr "我们现在可以使用这个噪声函数代替上一节中的``cos``和``sin``。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+"有了噪音功能，我们已经有了一些看起来很酷的东西。 有很多细节，有点像丘陵或山"
+"区。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr "片段着色器"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+"顶点着色器和片段着色器之间的区别在于顶点着色器每个顶点运行并设置诸"
+"如“VERTEX”（位置）和“正常”的属性，而片段着色器按像素运行，最重要的是， 设置："
+"ref：`Mesh <class_MeshInstance>`的``ALBEDO``颜色。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+"现在让我们看一下：ref：`Mesh <class_MeshInstance>`用常规着色器而不是线框。 将"
+"视口设置回“显示正常”。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+"：ref：`Mesh <class_MeshInstance>`看起来是完全白色的，因为片段着色器将每个像"
+"素着色为白色，但如果每个像素都是白色，我们就会丢失详细信息：ref：`Mesh "
+"<class_MeshInstance>`。 因此，让我们根据顶点着色器中计算的高度为每个像素着"
+"色。 我们通过在顶点着色器中设置``COLOR``变量来实现。 并通过将片段着色器中"
+"的“ALBEDO”设置为计算的“COLOR”变量。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+"通过这个更改，我们可以看到：ref：`Mesh <class_MeshInstance>`的细节，即使没有"
+"显示：ref：`Mesh <class_MeshInstance>`的线框。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+"统一变量允许您将数据从游戏传递到着色器。 它们对于控制着色器效果非常有用。 制"
+"服几乎可以是着色器中可以使用的任何数据类型。 要使用制服，请使用关键字"
+"``uniform``在：ref：`Shader <class_Shader>`中声明它。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr "让我们制作一个改变地形高度的制服。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+"Godot允许你用值初始化一个制服，这里``height_scale``设置为``0.5``。 您可以通过"
+"在与着色器对应的材质上调用函数``set_shader_param``来设置gdscript中的制服。 从"
+"gdscript传递的值优先于用于在着色器中初始化它的值。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+"请记住，传递给``set_shader_param``的字符串必须与：ref：`Shader "
+"<class_Shader>`中的统一变量的名称匹配。 您可以在：ref：`Shader "
+"<class_Shader>`中的任何位置使用统一变量。 在这里，我们将使用它来设置高度值，"
+"而不是任意乘以“0.5”。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+"地形应该看起来完全一样，但现在我们可以轻松控制高度。 这里是``height_scale``设"
+"置为``1``的相同地形："
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr "在这里，``height_scale``设置为``0.2``："
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+"使用制服我们甚至可以改变每帧的值来设置地形的高度。 结合：ref：`Tweens "
+"<class_Tween>`这对简单的动画特别有用。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr "与光交互"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+"作为本教程的最后一部分，我们尝试设置地形以与光交互。 首先，我们将向场景中添"
+"加：ref：`OmniLight <class_OmniLight>`。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+"您应该注意到没有任何变化，这是因为我们在本教程的开头将``render_mode``设置为"
+"``unshaded``，让我们删除它。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+"它现在看起来稍微好一点，你可以看到影响地形的光线，并且它因天空而变成了蓝色。 "
+"问题是光线正在影响地形，好像它是一个平面。 这是因为灯光着色器使用：ref："
+"`Mesh <class_MeshInstance>`的法线来计算光。 法线存储在：ref：`Mesh "
+"<class_MeshInstance>`中，但是我们正在改变着色器中的：ref：`Mesh "
+"<class_MeshInstance>`的形状，因此法线不再正确。 要解决此问题，我们需要重新计"
+"算着色器中的法线。 Godot让我们很容易，我们所要做的就是计算新法线并在顶点着色"
+"器中将``NORMAL``设置为该值。 通过``NORMAL``设置，戈多将为我们完成所有困难的灯"
+"光计算。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+"为了从噪声中计算法线，我们将使用一种称为“中心差异”的技术。 这很常用，特别是在"
+"像shadertoy这样的地方，用于计算着色器中的法线。 我们要做的是计算“x”和“z”方向"
+"顶点周围四个点的噪声，然后计算顶点的斜率。 毕竟法线只是噪音斜率的指标。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr "我们在顶点着色器中用一条线计算法线。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+"变量``e``只是更容易从``VERTEX``中添加和减去正确的值。 将``e``设置为较低的数字"
+"将增加法线的细节水平。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr "使用“NORMAL”计算地形现在看起来像："
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+"这看起来仍然不是我们想要的。 这里的问题是噪声变化比顶点变化得快。 因此，当我"
+"们计算“VERTEX”点时的法线时，它与我们在final中看到的不一致：ref：`Mesh "
+"<class_MeshInstance>`。 为了解决这个问题，我们添加了更多顶点。 下面的图像是"
+"用：ref：`Mesh <class_MeshInstance>`，``subdivision``设置为``100``。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr "现在我们可以拖动灯光，灯光会自动更新。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+"如果你缩小相机，你可以看到：ref：`Mesh <class_MeshInstance>`现在看起来像一个"
+"小地形。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+"这就是本教程的一切。 希望您了解戈多的顶点着色器的基础知识。 作为进一步的练习"
+"尝试从gdscript更改``height_scale``，尝试使用不同的：ref：`Primitive Meshes "
+"<class_PrimitiveMesh>`，并尝试使用自己的函数来计算``height``。"
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+"有关如何在Godot中使用着色器的更多信息，请查看：ref：`doc_shading_language`页"
+"面。"
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr "网络"
@@ -60420,11 +60508,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr "开始编译"
 
@@ -60660,16 +60748,15 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
-"我们将关注Godot 3.0中提供的NativeScript 1.0。 Godot 3.1将会看到NativeScript "
-"1.1的引入，它带来了许多改进。 我们将在正式发布后更新本教程，但整体结构仍然类"
-"似。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
@@ -60677,35 +60764,27 @@ msgstr ""
 "您可以在 `GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_上下"
 "载我们将在本教程中创建的完整示例。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr "设置项目"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr "您需要一些先决条件："
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr "Godot 3.x可执行文件，"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr "一个C ++编译器，"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr "SCons作为构建工具，"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-"`godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_ 的副本，"
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
 "godot-cpp>`_."
@@ -60713,7 +60792,7 @@ msgstr ""
 "`godot-cpp repository <https://github.com/GodotNativeTools/godot-cpp>`_ 的副"
 "本。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
@@ -60721,27 +60800,29 @@ msgstr ""
 "另请参阅：ref：`编译 <toc-devel-compiling>` 因为构建工具与从源代码编译Godot所"
 "需的构建工具相同。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
+#, fuzzy
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 "您可以从GitHub下载这些存储库，或让Git为您完成工作。 请注意，这些存储库现在对"
 "于不同版本的Godot具有不同的分支。 为早期版本的Godot编写的GDNative模块将在较新"
 "版本中运行（除了3.0和3.1之间的ARVR接口的一次重大更改），但反之亦然，因此请确"
 "保下载正确的分支。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr "如果您使用Git对项目进行版本控制，最好将它们添加为Git子模块："
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -60751,37 +60832,28 @@ msgstr ""
 "如果您决定只下载存储库或将它们克隆到项目文件夹中，请确保文件夹布局与此处描述"
 "的相同，因为我们将在此处展示的代码假定项目遵循此布局。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+#, fuzzy
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr "确保你克隆递归以拉入两个存储库：.. code-block :: none"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
+#, fuzzy
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
-msgstr ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
-msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 "我添加了``-b 3.0``作为示例，说明如何为特定版本的Godot选择特定分支。 另外"
 "``godot-cpp``现在包含``godot_headers``作为嵌套子模块，如果你手动下载它们，请"
 "确保在``godot-cpp``文件夹中放置``godot_headers``。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
+#, fuzzy
 msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
@@ -60789,7 +60861,7 @@ msgstr ""
 "您的文件夹中，请确保保持文件夹布局与我在此处设置的相同，因为我们将在此处展示"
 "的代码假定项目具有此布局。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
@@ -60797,21 +60869,21 @@ msgid ""
 msgstr ""
 "如果从介绍中指定的链接克隆示例，子模块不会自动初始化。 您需要执行以下命令："
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr "这会将这两个存储库克隆到您的项目文件夹中。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr "构建C ++绑定"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr "现在我们已经下载了我们的先决条件，现在是构建C ++绑定的时候了。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
@@ -60820,7 +60892,7 @@ msgstr ""
 "存储库包含当前Godot版本的元数据副本，但如果您需要为较新版本的Godot构建这些绑"
 "定，只需调用Godot可执行文件："
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
@@ -60829,7 +60901,7 @@ msgstr ""
 "将生成的``api.json``文件放在项目文件夹中，并将``use_custom_api_file = yes "
 "custom_api_file = .. / api.json``添加到下面的scons命令中。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
@@ -60837,7 +60909,7 @@ msgstr ""
 "要生成和编译绑定，请使用此命令（根据您的操作系统将``<platform>``替换为"
 "``windows``，``x11``或``osx``）："
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
@@ -60846,17 +60918,23 @@ msgstr ""
 "这一步将需要一段时间。 完成后，你应该有一个静态库，可以编译到你的项目中，存储"
 "在``godot-cpp / bin /``中。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr "在将来的某个时刻，已编译的二进制文件将可用，使此步骤可选。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr "创建一个简单的插件"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
@@ -60864,7 +60942,7 @@ msgstr ""
 "现在是构建实际插件的时候了。 我们首先创建一个空的Godot项目，我们将在其中放置"
 "一些文件。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
@@ -60872,7 +60950,7 @@ msgstr ""
 "打开戈多并创建一个新项目。 对于这个例子，我们将它放在我们的GDNative模块的文件"
 "夹结构中名为``demo``的文件夹中。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
@@ -60880,7 +60958,7 @@ msgstr ""
 "在我们的演示项目中，我们将创建一个包含名为“Main”的节点的场景，我们将其保存为"
 "``main.tscn``。 我们稍后再回过头来看看。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
@@ -60888,7 +60966,7 @@ msgstr ""
 "回到顶级GDNative模块文件夹，我们还将创建一个名为``src``的子文件夹，我们将在其"
 "中放置源文件。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
@@ -60896,7 +60974,7 @@ msgstr ""
 "你现在应该在你的GDNative模块中有``demo``，``godot-cpp``，``godot_headers``和"
 "``src``目录。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
@@ -60904,7 +60982,7 @@ msgstr ""
 "在``src``文件夹中，我们将首先为我们将要创建的GDNative节点创建头文件。 我们将"
 "它命名为``gdexample.h``："
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -60915,67 +60993,72 @@ msgstr ""
 "后，我们包含``Sprite.hpp``，它包含对Sprite类的绑定。 我们将在我们的模块中扩展"
 "这个类。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 "我们使用命名空间``godot``，因为GDNative中的所有内容都在此命名空间中定义。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
+#, fuzzy
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 "然后我们有了我们的类定义，它通过容器类从我们的Sprite继承。 我们稍后会看到一些"
 "副作用。 这也是NativeScript 1.1中将要改进的主要部分。 ``GODOT_CLASS``宏为我们"
 "设置了一些内部事物。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr "之后，我们声明一个名为``time_passed``的成员变量。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
+#, fuzzy
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 "在下一个块中我们定义了我们的方法，我们显然已经定义了构造函数和析构函数，但是"
 "还有其他两个函数可能看起来很熟悉。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
+#, fuzzy
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 "第一个是``_register_methods``，这是一个静态函数，戈多将调用它来找出可以在我们"
 "的NativeScript上调用哪些方法以及它暴露的属性。 第二个是我们的``_process``函"
 "数，它与你在GDScript中习惯的``_process``函数完全相同。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+#, fuzzy
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr "所以，让我们通过创建``gdexample.cpp``文件来实现我们的函数："
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
+#, fuzzy
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 "这个应该是直截了当的。 我们正在实现我们在头文件中定义的每个类的方法。 注意"
 "``register_method``调用**必须**公开``_process``方法，否则Godot将无法使用它。 "
 "但是，我们不必告诉Godot我们的构造函数和析构函数。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -60991,11 +61074,12 @@ msgstr ""
 "类; ``owner``指向我们脚本所涉及的实际Sprite节点。 在即将发布的NativeScript "
 "1.1中，可以在我们的类上直接调用``set_position``。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
+#, fuzzy
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
@@ -61004,7 +61088,7 @@ msgstr ""
 "现了``gdexample``一样。 我们现在需要的是一小段代码，告诉Godot我们的GDNative插"
 "件中的所有NativeScripts。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
@@ -61012,7 +61096,7 @@ msgstr ""
 "请注意，我们这里没有使用``godot``命名空间，因为这里实现的三个函数需要在没有命"
 "名空间的情况下定义。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -61024,7 +61108,7 @@ msgstr ""
 "``godot_gdnative_terminate``函数。 我们在这里所做的只是解析我们的绑定模块中的"
 "函数来初始化它们，但您可能需要根据需要设置更多内容。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -61035,11 +61119,11 @@ msgstr ""
 "中调用一个函数来执行它常用的东西。 之后，我们为库中的每个类调用函数"
 "``register_class``。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr "编译插件"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -61052,7 +61136,14 @@ msgstr ""
 "SConstruct>`我们已经准备好了。 我们将在后续教程中介绍如何使用这些构建文件的更"
 "可定制的详细示例。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
@@ -61061,11 +61152,11 @@ msgstr ""
 "一旦你下载了``SConstruct``文件，除了``godot-cpp``，``godot_headers``和"
 "``demo``之外，把它放在你的GDNative模块文件夹中，然后运行："
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr "您现在应该能够在``demo / bin / <platform>``中找到该模块。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
@@ -61074,11 +61165,11 @@ msgstr ""
 "在这里，我们编译了godot-cpp和我们的gdexample库作为调试版本。 对于优化的构建，"
 "您应该使用``target = release``开关编译它们。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr "使用GDNative模块"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
@@ -61087,7 +61178,7 @@ msgstr ""
 "在我们跳回Godot之前，我们需要在``demo / bin /``中再创建两个文件。 两者都可以"
 "使用Godot编辑器创建，但直接创建它们可能会更快。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
@@ -61095,7 +61186,7 @@ msgstr ""
 "第一个是一个文件，让Godot知道应该为每个平台加载什么动态库，并称为``gdexample."
 "gdnlib``。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -61108,7 +61199,7 @@ msgstr ""
 "现在应该留在``godot_``。 如果更改此设置，则需要重命名用作入口点的各种函数。 "
 "这是为iPhone平台添加的，因为它不允许部署动态库，但GDNative模块是静态链接的。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -61120,7 +61211,7 @@ msgstr ""
 "置。 导出项目时，它也会导致* just *导出文件，这意味着数据包不会包含与目标平台"
 "不兼容的库。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -61130,14 +61221,14 @@ msgstr ""
 "最后，``dependencies``部分允许您命名应包含的其他动态库。 当您的GDNative插件实"
 "现其他人的库并要求您为项目提供第三方动态库时，这一点非常重要。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 "如果你双击Godot中的``gdexample.gdnlib``文件，你会看到还有更多的选项要设置："
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
@@ -61146,12 +61237,13 @@ msgstr ""
 "我们需要创建的第二个文件是我们添加到插件中的每个NativeScript使用的文件。 我们"
 "将它命名为``gdexample.gdns``用于我们的gdexample NativeScript。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
+#, fuzzy
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
@@ -61160,7 +61252,7 @@ msgstr ""
 "含我们的NativeScript。 它还定义了``class_name``，它标识了我们想要使用的插件中"
 "的NativeScript。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
@@ -61168,7 +61260,7 @@ msgstr ""
 "是时候跳回戈多了。 我们在开始时加载我们创建的主场景，现在为场景添加一个"
 "Sprite："
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
@@ -61177,15 +61269,213 @@ msgstr ""
 "我们要将Godot徽标指定给这个精灵作为我们的纹理，禁用``centered``属性并将我们的"
 "``gdexample.gdns``文件拖到精灵的``script``属性中："
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr "我们终于准备好运行这个项目了："
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+#, fuzzy
+msgid "Adding properties"
+msgstr "节点属性"
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr "下一步"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
@@ -61194,7 +61484,7 @@ msgstr ""
 "以上只是一个简单的例子，但我们希望它向您展示基础知识。 您可以在此示例的基础上"
 "构建完整的脚本，以使用C ++控制Godot中的节点。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -63476,7 +63766,7 @@ msgstr ""
 "因此，如果你想要自己构建 Godot 的话，请持一个开放的态度，至少稍微熟悉一下这个"
 "构建系统。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -63488,7 +63778,7 @@ msgstr ""
 "`doc_compiling_for_uwp`, :ref:`doc_compiling_for_web`, :ref:"
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
@@ -63498,11 +63788,11 @@ msgstr ""
 "Command Prompt for VS 2017``  这类工具（具体命令视你安装的版本来定）， 而不能"
 "直接使用通用的 Windows 命令提示符。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr "选择构建平台"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -63513,17 +63803,17 @@ msgstr ""
 "测到当当前环境不支持的平台，那么这个平台将不会显示在可构建的平台列表中。 本文"
 "的的后续部分将介绍各个平台的构建要求。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr "SCons 构建系统可通过调用 ``scons`` 命令来启动。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr "但是，除了列出可用的平台之外，这并不会执行任何构建任务。例如："
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
@@ -63531,7 +63821,7 @@ msgstr ""
 "我们通过传递平台参数（ 添加``platform=`` 或者缩写 ``p=`` ）来让 Scons 执行对"
 "应平台（例如 x11 ）的构建任务:"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -63542,25 +63832,25 @@ msgstr ""
 "度更快，请使用 ``-j <cores>`` 参数指定构建任务要使用多少个CPU核心。 或者只是"
 "让它使用一个核心，这样你可以继续使用你的电脑的做其他事情 :)"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr "例如启动 4 核进行构建："
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr "输出的程序"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr "构建所得到的二进制文件将被放置在 bin/ 子目录中，通常使用这种命名约定："
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr "对于上面所说的构建任务，将输出下面这样的二进制文件："
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
@@ -63568,11 +63858,11 @@ msgstr ""
 "文件名描述了这个二进制文件是 X11 平台的、它没有进行编译优化、它带有工具功能"
 "（整个 Godot 编辑器）、并且它是针对64位架构进行构建的结果。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr "同理，同样的构建配置在 Windows 上的构建文件是这样的。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -63585,7 +63875,7 @@ msgstr ""
 "游戏到其他平台的导出模板（可以从`godotengine.org <https://godotengine.org/"
 ">`__下载到，也可以自己构建它们）。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
@@ -63593,7 +63883,7 @@ msgstr ""
 "除此之外，可以在所有的构建目标中有几个标准选项可以进行设置，下面将对此进行说"
 "明。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
@@ -63603,15 +63893,15 @@ msgstr ""
 "用。 禁用工具选项后构建得到的二进制文件会更小，因为它不包括游戏编辑器和项目管"
 "理器功能。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr "构建目标 (target)"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr "构建目标控制的是编译器的调试和优化选项， 它支持这些模式："
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
@@ -63619,7 +63909,7 @@ msgstr ""
 "**debug**: 带有C ++调试符号的构建，支持运行时检查（执行检查和错误报告）同时不"
 "进行编译任何优化。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
@@ -63628,7 +63918,7 @@ msgstr ""
 "**release_debug**: 不带C ++调试符号和编译器优化，但保持运行时检查（执行检查和"
 "错误报告）。 官方发布的二进制文件就是使用这种配置进行构建的。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
@@ -63638,7 +63928,7 @@ msgstr ""
 "不能与``tools = yes``一起使用，因为这些工具需要一些调试功能和运行时检查才能运"
 "行。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
@@ -63647,11 +63937,11 @@ msgstr ""
 "根据些选项的配置会在二进制文件名中附加 “.debug” 后缀（用于调试）或 “."
 "tools”（用于启用工具的调试）。 当启用优化（发布版）时，它会附加“.opt”后缀。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr "位 (bits)"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
@@ -63659,15 +63949,15 @@ msgstr ""
 "位选项控制的是构建结果的二进制文件指出的CPU或操作系统的版本。它是针对桌面平台"
 "的配置，在其他平台会被忽略掉。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr "**32**: 构建支持32位系统的二进制文件。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr "**64**:  构建支持64位系统的二进制文件。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
@@ -63677,17 +63967,17 @@ msgstr ""
 "你所使用的系统（如果不是交叉编译的话），在Mac上它默认为64位，在Windows上它默"
 "认为32位。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr "这项配置会在构建结果的二进制文件名中添加  \".32\" 或  \".64\" 后缀。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr "其他构建选项"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
@@ -63696,13 +63986,13 @@ msgstr ""
 "您还可以使用其他几个构建选项来配置Godot的构建方式（编译器，调试选项等）以及要"
 "包含/禁用的功能。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr "检查``scons --help``的输出，了解您愿意编译的版本的每个选项的详细信息。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -63713,7 +64003,7 @@ msgstr ""
 "到。 此外，由于种种原因你可能想要自己构建你的导出模板（可能你想要构建未发布的"
 "新版本、你要使用模块（modules）、你不信任我们编译的包是否安全）。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
@@ -63721,7 +64011,7 @@ msgstr ""
 "如果你下载过官方的导出模板压缩包，解压后你会发现里面大多是各个平台通过编译优"
 "化二进制文件或者对应平台的软件包："
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
@@ -63730,7 +64020,7 @@ msgstr ""
 "如要自己创建这些文件，只需按照该教程的各个平台的详细说明进行操作即可。 每个平"
 "台的教程都有介绍如何创建导出模板。"
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -63778,11 +64068,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr "`SCons <https://www.scons.org>`__构建系统。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr "设置SCons"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -63796,7 +64098,7 @@ msgstr ""
 "件夹中），并提供一个名为``scons.bat``的批处理文件。 可以将此文件的位置添加到"
 "路径中，也可以将其与解释器可执行文件一起复制到“C：\\ Python”。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
@@ -63805,7 +64107,7 @@ msgstr ""
 "要检查是否已正确安装Python和SCons，可以在Windows命令提示符（``cmd.exe``）中键"
 "入``python --version``和``scons --version``。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
@@ -63813,11 +64115,11 @@ msgstr ""
 "如果上面的命令不起作用，请确保在安装后将Python添加到PATH环境变量中，然后再次"
 "检查。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr "设置Pywin32"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -63830,7 +64132,7 @@ msgstr ""
 "装程序可执行文件中正确安装 `它。 <https://github.com/mhammond/pywin32/"
 "releases>`__"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -63841,7 +64143,7 @@ msgstr ""
 "构建的最新版本Pywin32。该可执行安装程序将命名为' pywin32-221.win32-py2.7.exe "
 "' '。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
@@ -63851,11 +64153,11 @@ msgstr ""
 "exe``。 更改`py``数字以安装您的Python版本（通过上面提到的``python --version``"
 "检查）。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr "安装Visual Studio警告"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -63870,7 +64172,7 @@ msgstr ""
 "vcblog/2015/07/24/setup-changes-in-visual-studio-2015-affecting-c-developers/"
 ">`__ 在Visual Studio 2015中。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -63882,18 +64184,18 @@ msgstr ""
 "序，它将为您提供**修改**按钮选项。 从“添加/删除程序”运行安装只会为您提供“修"
 "复”选项，该选项对您的问题无效。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 "如果您正在使用Express，请确保您拥有可以为*** C ++，Desktop ***编译的版本。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr "下载戈多的来源"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
@@ -63902,13 +64204,13 @@ msgstr ""
 "`戈多的 <https://github.com/godotengine/godot>`__来源托管在GitHub上。 建议通"
 "过`Git <https://git-scm.com/>`__下载（克隆）。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr "从现在开始，本教程将假设您将源放入``C：\\ godot``。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
@@ -63917,7 +64219,7 @@ msgstr ""
 "从Windows命令提示符（``cmd.exe``）编译SCons将无法开箱即用，因为SCons和Visual "
 "C ++编译器将无法找到编译所需的环境变量和可执行文件。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -63927,27 +64229,27 @@ msgstr ""
 "因此，您需要启动Visual Studio命令提示符。 它设置SCons定位编译器所需的环境变"
 "量。 它应该被称为类似于以下名称之一（对于您的各自版本的Visual Studio）："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr "“VS2013的开发人员命令提示符”"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr "“VS2013 x64 Native Tools命令提示符”"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr "“VS2013 x86 Native Tools命令提示符”"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr "“VS2013 x64交叉工具命令提示”"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr "“VS2013 x86交叉工具命令提示”"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
@@ -63955,7 +64257,7 @@ msgstr ""
 "您应该能够在开始菜单中找到至少适用于您的Visual Studio版本的开发人员命令提示"
 "符。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
@@ -63964,7 +64266,7 @@ msgstr ""
 "但是Visual Studio有时似乎没有安装上述某些快捷方式，除了开发菜单搜索选项自动搜"
 "索的这些位置的开发者控制台："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
@@ -63973,7 +64275,7 @@ msgstr ""
 "如果您找到了Developer Console，它现在将创建一个32位版本的Godot，但如果您需要"
 "64位版本，则可能需要手动设置提示以便于访问。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
@@ -63981,17 +64283,17 @@ msgstr ""
 "如果您没有看到某些快捷方式，“下面的提示如何实际工作”部分将说明如何在需要时设"
 "置这些提示。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr "关于Developer / Tools命令提示符和Visual C ++编译器"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr "关于这些控制台和Visual C ++编译器，您需要了解一些事项。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -64002,7 +64304,7 @@ msgstr ""
 "``cl.exe``（Visual C ++编译器）将为不同的架构（32位x86或64位x86）编译Godot ;"
 "不支持ARM编译器）。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
@@ -64010,7 +64312,7 @@ msgstr ""
 "** Developer Command Prompt **将使用32位Visual C ++编译器构建32位版本的"
 "Godot。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -64021,7 +64323,7 @@ msgstr ""
 "符）时，将使用提示（如上所述）。 对于64位cl.exe，它将编译64位可执行文件（x64 "
 "Native Tools命令提示符）。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -64032,18 +64334,18 @@ msgstr ""
 "时，将使用** Cross Tools **。 您可能已经熟悉，32位Windows无法运行64位可执行文"
 "件，但您仍可能需要为它们进行编译。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr "例如："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr "“VS2013 x64交叉工具命令提示符”将使用将编译64位应用程序的32位cl.exe。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
@@ -64052,7 +64354,7 @@ msgstr ""
 "“VS2013 x86交叉工具命令提示符”将使用将编译32位应用程序的64位cl.exe。 如果您运"
 "行的是32位Windows，则此选项非常有用。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -64063,7 +64365,7 @@ msgstr ""
 "64位Windows可以运行任何32位应用程序。 32位Windows无法运行64位可执行文件，因此"
 "Visual Studio安装程序甚至不会为某些提示安装快捷方式。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
@@ -64073,11 +64375,11 @@ msgstr ""
 "Godot以获得正确的架构。 如果您还不确定Cross Compile Prompts究竟做了什么，请仅"
 "使用Native Prempts。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr "运行SCons"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
@@ -64085,7 +64387,7 @@ msgstr ""
 "进入** Developer Console / Tools Console Prompt **后，转到引擎源代码的根目录"
 "并输入："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
@@ -64093,7 +64395,7 @@ msgstr ""
 "提示：如果你安装了“Pywin32 Python Extension”，你可以附加-j命令来指示SCons运行"
 "这样的并行构建："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -64104,7 +64406,7 @@ msgstr ""
 "译Godot。 如果您设置了“Pywin32 Python Extension”，请随意将-j选项添加到您在下"
 "面看到的任何SCons命令中。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -64116,15 +64418,15 @@ msgstr ""
 "``godot.windows.tools.32.exe``或``godot.windows.tools。64.exe``。 SCons将自动"
 "检测环境（提示）的设置编译器体系结构，并将构建相应的可执行文件。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 "此可执行文件包含整个引擎，并且运行时没有任何依赖性。 执行它将调出项目经理。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
@@ -64133,11 +64435,11 @@ msgstr ""
 "如果您正在编译Godot用于生产用途，那么您可以通过添加SCons选项``target = "
 "release_debug``来使最终的可执行文件更小更快。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr "提示如何实际工作"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -64153,7 +64455,7 @@ msgstr ""
 "为** VsDevCmd.bat **的文件，但Godot / SCons不需要这个批处理文件启用的其他工"
 "具。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
@@ -64162,13 +64464,13 @@ msgstr ""
 "由于您可能正在使用Visual Studio 2013或2015，如果您需要手动重新创建它们，请使"
 "用以下文件夹，或将它们放在桌面/任务栏上："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr "在所需位置的空白处按“鼠标右键/新建/快捷方式”，开始创建快捷方式。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
@@ -64177,19 +64479,19 @@ msgstr ""
 "然后将以下这些命令之一复制到快捷方式创建向导的“路径”和“名称”部分中所需的相应"
 "工具，并根据需要修复批处理文件的路径。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr "Visual Studio 2013位于“Microsoft Visual Studio 12.0”文件夹中。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr "Visual Studio 2015位于“Microsoft Visual Studio 14.0”文件夹中。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr "等等"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
@@ -64198,7 +64500,7 @@ msgstr ""
 "创建快捷方式后，在快捷方式的属性中，可以通过在快捷方式上单击鼠标右键来访问该"
 "快捷方式，可以选择命令提示符的起始目录（“开始”字段）。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -64210,7 +64512,7 @@ msgstr ""
 "中不可用。 在重新创建命令之前，请确保其中一个位置中存在“cl.exe”可执行文件，它"
 "们是您要从命令提示符构建的体系结构的实际编译器。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
@@ -64218,11 +64520,11 @@ msgstr ""
 "如果您想知道这些提示快捷方式的作用，他们会使用``\\ k``选项调用``cmd.exe``并让"
 "它运行批处理文件。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr "如何运行戈多的自动构建"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
@@ -64230,39 +64532,39 @@ msgstr ""
 "如果只需要通过批处理文件或直接在Windows命令提示符下运行编译过程，则需要使用以"
 "下命令："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr "使用以下参数之一："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr "x86（32位cl.exe编译为32位架构）"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr "amd64（为64位架构编译的64位cl.exe）"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr "x86_amd64（为64位架构编译的32位cl.exe）"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr "amd64_x86（为32位架构编译的64位cl.exe）"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr "在那之后，你可以运行SCons："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr "或者你可以一起运行它们："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr "在Visual Studio或其他IDE中进行开发"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
@@ -64271,7 +64573,7 @@ msgstr ""
 "对于大多数项目，只使用脚本就足够了，但是当需要C++开发时，为了创建模块或扩展引"
 "擎，通常需要使用IDE。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
@@ -64279,7 +64581,7 @@ msgstr ""
 "您可以通过使用``vsproj = yes``参数运行SCons来创建Visual Studio解决方案，如下"
 "所示："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -64290,7 +64592,7 @@ msgstr ""
 "Studio ** Build **按钮构建Godot。 但是，请确保已安装Pywin32，以便并行（-j）构"
 "建正常工作。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -64302,11 +64604,11 @@ msgstr ""
 "SCons。 如果出错，请从其他构建配置（debug，release_debug，release）或体系结构"
 "（Win32 / x64）中复制命令。 它们是等价的。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr "从其他操作系统交叉编译Windows"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -64317,37 +64619,37 @@ msgstr ""
 "php>`_，它通常包含32位和64位变体。 包名称可能因您的发行版而异，以下是一些已知"
 "的发行版："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr "**Arch**"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr "**Debian** / **Ubuntu**"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr "**Fedora**"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr "**macOS**"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr "**Mageia**"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr "在允许您尝试编译之前，SCons将在您的``$ PATH``中检查以下二进制文件："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
@@ -64356,7 +64658,7 @@ msgstr ""
 "如果二进制文件不在``$ PATH``中（例如``/ usr / bin``），你可以定义以下环境变量"
 "来给构建系统一个提示："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
@@ -64365,14 +64667,14 @@ msgstr ""
 "为了确保您正确地执行操作，在shell中执行以下操作应该会生成一个正常工作的编译器"
 "（版本输出可能因您的系统而异）："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr "故障排除"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
@@ -64381,49 +64683,49 @@ msgstr ""
 "某些版本的Ubuntu的交叉编译可能会导致 `此错误 <https://github.com/godotengine/"
 "godot/issues/9258>`_，因为默认配置缺乏对POSIX线程的支持。"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr "您可以按照这些说明更改该配置，对于32位："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr "而对于64位："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr "创建Windows导出模板"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr "Windows导出模板是通过将Godot编译为release来创建的，具有以下标志："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr "（使用Mingw32命令提示符，使用bits参数）"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr "（使用Mingw-w64命令提示符，使用bits参数）"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr "（使用Visual Studio命令提示正确的体系结构，注意缺少bits参数）"
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr "如果您打算更换标准模板，请将这些模板复制到："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr "使用以下名称："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
@@ -64432,7 +64734,7 @@ msgstr ""
 "此外，如果你正在开发自定义模块或修改引擎的其他 C++ 代码，则可以在此处将你编译"
 "好的二进制文件配置为自定义导出模板："
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -64503,37 +64805,37 @@ msgstr "*可选* - libudev（使用``udev = yes``构建）"
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr "*可选* - yasm（用于WebM SIMD优化）"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr "各个发型版的安装指令"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr "**FreeBSD**"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr "**Gentoo**"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr "**OpenBSD**"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr "**openSUSE**"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr "**Solus**"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr "启动终端，然后进入引擎源代码的根目录。键入下面的指令："
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -64544,8 +64846,8 @@ msgstr ""
 "CPU中有核心一样，如果不是一两个。 随意将``-j``选项添加到您在下面看到的任何"
 "SCons命令。"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
@@ -64554,38 +64856,38 @@ msgstr ""
 "如果一切顺利，编译结果将存放在 ``bin`` 目录下。 这个可执行文件包含了整个引"
 "擎，无需任何依赖项。 执行它将会启动项目管理器。"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr "如果你希望使用 Clang 而不是 GCC 编译器， 可以使用这个命令："
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 "在 OpenBSD 平台上必须使用 Clang，否则在构建字体相关的依赖时会遇到一些麻烦。"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr "构建导出模板"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 "要构建 X11 （Linux，\\*BSD）平台的导出模板， 执行构建系统时需要带上这些参数："
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr "（ 32 位 ）"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr "( 64 位 )"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
@@ -64593,12 +64895,12 @@ msgstr ""
 "请注意，跨CPU位数( 64/32)编译不总是这样直截了当，这可能还需要你通过 "
 "``chroot`` 切换编译环境。"
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr "要创建导出模板，需要你手动把编译出来的二进制文件拷贝到这里："
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
@@ -64606,7 +64908,7 @@ msgstr ""
 "并且还需要将文件命名成这样（在 Godot 中， \\*BSD 平台也被视为 \"Linux "
 "X11\"）："
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -64628,7 +64930,7 @@ msgstr "Python 2.7+或Python 3.5+"
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr "或者更轻量的Command Line Tools for Xcode"
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
@@ -64638,11 +64940,11 @@ msgstr ""
 "app``的模版来做。像这样一个为“.64”优化的二进制程序的构建（scons p=osx "
 "target=release_debug），通常这么做："
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr "同时为32位和64位编译"
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -64653,11 +64955,11 @@ msgstr ""
 "为“.64”的。如果要编译同时包含32位和64位代码的“.fat”可执行文件，可以通过在"
 "scons命令中指定位设定来实现，如下所示："
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr "交叉编译"
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -64668,7 +64970,7 @@ msgstr ""
 "`OSXCross <https://github.com/tpoechtrager/osxcross>`__才能使用macOS作为目"
 "标。 首先，按照说明安装它："
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
@@ -64677,21 +64979,21 @@ msgstr ""
 "在您机器的某个地方克隆 `OSXCross存储库 <https://github.com/tpoechtrager/"
 "osxcross>`（或下载一个zip文件并将其解压缩到某处），例如："
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 "按照说明打包SDK：https：//github.com/tpoechtrager/osxcross#packaging-the-sdk"
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 "按照说明安装OSXCross：https：//github.com/tpoechtrager/osxcross#installation"
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
@@ -64700,11 +65002,11 @@ msgstr ""
 "之后，您需要将``OSXCROSS_ROOT``定义为OSXCross安装的路径（您克隆存储库/提取zip"
 "的位置），例如："
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr "现在您可以像通常那样使用SCons进行编译："
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -64772,20 +65074,20 @@ msgid ""
 msgstr ""
 "JDK 6或更高版本（OpenJDK或Oracle JDK） - JDK 9和10不适用于当前的Gradle。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr "设置构建系统"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr "将环境变量ANDROID_HOME设置为指向Android SDK。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr "将环境变量ANDROID_NDK_ROOT设置为指向Android NDK。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
@@ -64794,7 +65096,7 @@ msgstr ""
 "要在Windows上设置这些环境变量，请按Windows + R，键入“control system”，然后单"
 "击左窗格中的**高级系统设置**，然后在出现的窗口中单击**环境变量**。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -64806,27 +65108,11 @@ msgstr ""
 "android-ndk``。 / path / to / android-sdk和/ path / to / android-ndk是"
 "Android SDK和Android NDK放置在PC上的路径。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr "工具链"
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-"我们通常会尝试更新Godot Android构建代码，但Google经常更改其工具链版本，因此如"
-"果由于错误的工具链版本导致编译失败，请转到NDK目录并检查当前编号，然后设置以下"
-"环境变量："
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr "构建导出模板"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -64837,29 +65123,29 @@ msgstr ""
 "版本（`android_debug.apk`）。 编译标准导出模板是通过使用以下参数调用scons来完"
 "成的："
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr "发布模板（导出时使用“Debugging Enabled”OFF）"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr "（在Linux或macOS上，使用`./gradlew build`执行`gradlew`脚本）"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr "生成的APK位于："
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr "调试模板（导出时使用“Debugging Enabled”ON）"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr "编译速度更快"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -64870,11 +65156,11 @@ msgstr ""
 "SCons命令中添加``-jX``参数来加速编译，其中``X``是那个核的数量。 你想分配给编"
 "译，例如 ``scons -j4``。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr "添加对x86设备的支持"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
@@ -64883,14 +65169,14 @@ msgstr ""
 "如果您还想包含对x86设备的支持，请在使用Gradle构建APK之前再次使用"
 "``android_arch = x86``参数运行scons命令。 例如，对于发布模板："
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 "这将创建一个可在两个平台上运行的胖二进制文件，但会为APK增加大约6兆字节。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
@@ -64899,11 +65185,11 @@ msgstr ""
 "可能有必要清除两个APK编辑之间的构建缓存，因为一些用户在逐个构建两个导出模板时"
 "报告了问题。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr "使用导出模板"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -64914,17 +65200,17 @@ msgstr ""
 "APK。 如果您使用官方二进制文件作为编辑器，请确保安装匹配的导出模板，或者从同"
 "一版本构建自己的模板。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr "导出游戏时，Godot会打开APK，更改内部的一些内容并添加您的文件。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr "安装模板"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
@@ -64933,7 +65219,7 @@ msgstr ""
 "必须将新编译的模板（android_debug.apk和android_release.apk）复制到Godot的模板"
 "文件夹及其各自的名称。 templates文件夹可以位于："
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
@@ -64941,11 +65227,11 @@ msgstr ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
@@ -64953,7 +65239,7 @@ msgstr ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -64964,7 +65250,7 @@ msgstr ""
 "``version.py``的值（例如``3.0.5.stable`` 或``3.1.dev``）。 您还需要将相同的版"
 "本字符串写入导出模板旁边的``version.txt``文件。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
@@ -64972,7 +65258,7 @@ msgstr ""
 "但是，如果您正在编写自定义模块或自定义C ++代码，则可能需要将APK配置为自定义导"
 "出模板："
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
@@ -64981,49 +65267,49 @@ msgstr ""
 "你甚至不需要复制它们，你可以在Godot源文件夹的``bin \\``目录中引用生成的文件，"
 "这样下次构建时你将自动引用自定义模板。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr "应用程序未安装"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr "Android可能会抱怨应用程序未正确安装。 如果是，请检查以下内容："
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr "检查是否正确生成了调试密钥库。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr "检查jarsigner是否来自JDK 6,7或8。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr "如果仍然失败，请打开命令行并运行logcat："
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr "并在安装应用程序时检查输出。 应该在那里提出失败的原因。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr "如果你想不通，请寻求帮助。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr "申请立即退出"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr "如果应用程序运行但立即退出，则可能是以下原因之一："
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
@@ -65031,27 +65317,27 @@ msgstr ""
 "确保使用与编辑器版本匹配的导出模板; 如果您使用新的Godot版本，您* *也可以*更新"
 "模板。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr "libgodot_android.so不在``lib / armeabi-v7a``或``lib / armeabi``中"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr "设备不支持armv7（尝试为armv6编译自己）"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr "设备是Intel，apk是为ARM编译的。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr "无论如何，``adb logcat``也应该显示错误的原因。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr "编译失败"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
@@ -65059,7 +65345,7 @@ msgstr ""
 "在内核版本为4.3或更高版本的Linux系统上，编译可能会失败，并显示错"
 "误“pthread_create failed：资源暂时不可用。”"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
@@ -65068,7 +65354,7 @@ msgstr ""
 "这是因为Linux限制线程创建的方式发生了变化。 但您可以通过命令行更改这些限制。 "
 "请在开始之前仔细阅读本节内容。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
@@ -65077,7 +65363,7 @@ msgstr ""
 "首先打开一个终端，然后像往常一样开始编译（首先运行--clean可能是个好主意）。 "
 "编译时在终端中输入以下内容："
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
@@ -65085,7 +65371,7 @@ msgstr ""
 "输出应列出scons进程，其PID为输出中的第一个数字。 例如，输出中的PID 1077如下所"
 "示："
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
@@ -65093,11 +65379,11 @@ msgstr ""
 "现在，您可以使用另一个命令来增加允许生成scons的进程数。 您可以通过以下方式检"
 "查其当前限制:"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr "您可以使用以下命令增加这些限制："
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
@@ -65106,7 +65392,7 @@ msgstr ""
 "显然你应该用顶部的scons PID输出和你认为合适的限制来代替。 它们的形式为--"
 "nproc = soft：hard，其中soft必须小于或等于hard。 有关更多信息，请参见手册页。"
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -65129,15 +65415,15 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr "Xcode与iOS SDK和命令行工具。"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr "打开终端，转到引擎源代码的根目录并键入："
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr "用于调试版本，或："
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
@@ -65145,15 +65431,15 @@ msgstr ""
 "对于发布版本（检查``platform / iphone / detect.py``以获取用于每个配置的编译器"
 "标志）。"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr "或者，您可以运行"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr "用于模拟器可执行文件。"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -65168,18 +65454,18 @@ msgstr ""
 "它可以分三步完成，首先编译32位版本，然后编译64位版本，然后使用``lipo``将它们"
 "捆绑成一个胖二进制文件，所有这些步骤都可以使用以下命令执行："
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr "运行"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 "要在设备或模拟器上运行，请按照以下说明操作:: ref：`doc_exporting_for_ios`。"
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -65308,6 +65594,10 @@ msgstr "解压缩iOS SDK："
 msgid "Pack the SDK:"
 msgstr "打包SDK："
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr "工具链"
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr "构建cctools："
@@ -65408,7 +65698,7 @@ msgstr ""
 "`ANGLE source <https://github.com/Microsoft/angle>`__。 使用``ms_master``（默"
 "认）分支。 将其保存在没有空格的路径中以避免出现问题。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
@@ -65417,7 +65707,7 @@ msgstr ""
 "您需要为要构建的目标体系结构打开正确的Visual Studio提示符。 检查：ref："
 "`doc_compiling_for_windows`以查看这些提示是如何工作的。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
@@ -65426,7 +65716,7 @@ msgstr ""
 "UWP有三种目标体系结构：x86（32位），x64（64位）和ARM（32位）。 对于后者，您可"
 "以使用``x86_arm``或``amd64_arm``作为参数运行``vcvarsall.bat``来设置环境。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
@@ -65435,16 +65725,16 @@ msgstr ""
 "将``ANGLE_SRC_PATH``设置为您下载ANGLE源代码的目录。 构建过程还将构建ANGLE以生"
 "成所选体系结构所需的DLL。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr "设置完成后，与其他平台类似地运行SCons命令::"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr "创建UWP导出模板"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
@@ -65453,7 +65743,7 @@ msgstr ""
 "要使用编辑器导出，您需要正确构建包模板。 您需要使用``debug``和``release``模板"
 "的所有三种架构才能导出。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
@@ -65461,11 +65751,11 @@ msgstr ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr "重复其他架构。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
@@ -65474,7 +65764,7 @@ msgstr ""
 "最后你的``bin``文件夹将有``.exe``二进制文件，其名称类似于``godot.uwp.opt."
 "debug.32.x86.exe``（每个目标/拱的变体）。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -65487,7 +65777,7 @@ msgstr ""
 "％arch％``（``％arch％``可以是``Win32``，``x64``或``ARM``）下， 获取``libEGL."
 "dll``和``libGLESv2.dll``，将它们与可执行文件放在一起。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
@@ -65495,7 +65785,7 @@ msgstr ""
 "将``uwp_template``文件夹中的文件添加到ZIP中。 根据模板的目标/体系结构重命名生"
 "成的Zip ::"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -65507,11 +65797,11 @@ msgstr ""
 "`versionstring`是您编译导出模板的Godot版本 - 例如 对于Godot 3的alpha版"
 "本，“3.0.alpha”。如果您不想替换模板，可以在导出窗口中设置“自定义包”属性。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr "使用Visual Studio运行UWP应用程序"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -65522,7 +65812,7 @@ msgstr ""
 "Studio部署和启动它们。 如果您在Windows Phone或Xbox One等设备上进行测试，这可"
 "能是最简单的方法。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
@@ -65531,7 +65821,7 @@ msgstr ""
 "在ANGLE源文件夹中，打开``templates``并双击``install.bat``脚本文件。 这将为"
 "ANGLE应用程序安装Visual Studio项目模板。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -65542,7 +65832,7 @@ msgstr ""
 "并将其构建到Release / Win32目标。 如果您计划在设备上运行，则可能还需要为ARM构"
 "建它。 如果您对命令行感到满意，也可以使用MSBuild。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
@@ -65551,7 +65841,7 @@ msgstr ""
 "使用“App for OpenGL ES（Windows Universal）”项目模板创建一个新的Windows应用程"
 "序项目，该模板位于“Visual C ++ / Windows / Universal”类别下。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -65564,7 +65854,7 @@ msgstr ""
 "口中，将相对路径从“Debug_Win32”更改为“Release_Win32”（或设备"
 "的“Release_ARM``”）。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
@@ -65573,7 +65863,7 @@ msgstr ""
 "在相同的“二进制”过滤器中，选择“添加>现有项”并指向您拥有的UWP的戈多可执行文"
 "件。 在“属性”窗口中，将“内容”设置为“真”，以便它包含在项目中。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -65588,7 +65878,7 @@ msgstr ""
 "用你的Godot可执行文件）。 同时将``EntryPoint``属性更改为``GodotUWP.App``。 这"
 "将确保在应用程序启动时正确调用Godot可执行文件。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -65601,7 +65891,7 @@ msgstr ""
 "项目”命令将其全部包含在内，并将其“内容”属性设置为“True”，以便将它们复制到应用"
 "程序中。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -65613,7 +65903,7 @@ msgstr ""
 "序的“构建”选项。 您仍然必须至少构建一次以生成一些所需的文件，您可以通过右键单"
 "击“解决方案资源管理器”中的项目（*不是解决方案）并选择“构建”来实现。"
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -65649,7 +65939,7 @@ msgstr "`Python 2.7+或Python 3.5+ <https://www.python.org/>`__"
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr "`SCons <https://www.scons.org>`__构建系统"
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -65664,7 +65954,7 @@ msgstr ""
 "latest``时，或者由你的包管理器调用。 如果文件不存在，它也会在启动Emscripten的"
 "``emcc``程序时创建。"
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -65674,7 +65964,7 @@ msgstr ""
 "打开终端并导航到引擎源代码的根目录。 然后指示SCons构建JavaScript平台。 将"
 "``target``指定为发布版本的``release``或调试版本的``release_debug`` ::"
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
@@ -65684,7 +65974,7 @@ msgstr ""
 "于``eval（）``调用可能是一个安全问题，``javascript_eval``选项可用于构建而不需"
 "要单例::"
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -65695,21 +65985,21 @@ msgstr ""
 "目录中。 它的名字是``godot.javascript.opt.zip`` for release或``godot."
 "javascript.opt.debug.zip`` for debug。"
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr "最后，将zip存档重命名为``webassembly_release.zip``以获取发布模板::"
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr "调试模板的``webassembly_debug.zip`` ::"
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr "根据asm.js转换或LLVM后端构建"
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -65722,7 +66012,7 @@ msgstr ""
 "的工具将此代码转换为WebAssembly。 Emscripten会自动处理这两个进程，我们只需运"
 "行SCons。"
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -65736,7 +66026,7 @@ msgstr ""
 "此后端进行编译以LLVM的``.s``格式输出文件，使用名为``s2wasm``的工具将其转换为"
 "实际的WebAssembly。 Emscripten也管理这些进程，因此我们只调用SCons。"
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "
@@ -73461,6 +73751,40 @@ msgstr ""
 "`Zeef Godot Engine：由Andre Schmitz撰写的精选资源目录 <https://godot-engine."
 "zeef.com/andre.antonio.schmitz>`_"
 
+#~ msgid ""
+#~ "We'll be looking at NativeScript 1.0 which is available in Godot 3.0. "
+#~ "Godot 3.1 will see the introduction of NativeScript 1.1, which comes with "
+#~ "a number of improvements. We'll update this tutorial once it is "
+#~ "officially released, but the overall structure remains similar."
+#~ msgstr ""
+#~ "我们将关注Godot 3.0中提供的NativeScript 1.0。 Godot 3.1将会看到"
+#~ "NativeScript 1.1的引入，它带来了许多改进。 我们将在正式发布后更新本教程，"
+#~ "但整体结构仍然类似。"
+
+#~ msgid ""
+#~ "a copy of the `godot_headers repository <https://github.com/"
+#~ "GodotNativeTools/godot_headers>`_,"
+#~ msgstr ""
+#~ "`godot_headers repository <https://github.com/GodotNativeTools/"
+#~ "godot_headers>`_ 的副本，"
+
+#~ msgid ""
+#~ "mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -"
+#~ "b 3.0 https://github.com/GodotNativeTools/godot-cpp"
+#~ msgstr ""
+#~ "mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -"
+#~ "b 3.0 https://github.com/GodotNativeTools/godot-cpp"
+
+#~ msgid ""
+#~ "We usually try to keep the Godot Android build code up to date, but "
+#~ "Google changes their toolchain versions often, so if compilation fails "
+#~ "due to wrong toolchain version, go to your NDK directory and check the "
+#~ "current number, then set the following environment variable:"
+#~ msgstr ""
+#~ "我们通常会尝试更新Godot Android构建代码，但Google经常更改其工具链版本，因"
+#~ "此如果由于错误的工具链版本导致编译失败，请转到NDK目录并检查当前编号，然后"
+#~ "设置以下环境变量："
+
 #~ msgid ""
 #~ "Another reason is that, for distribution, the developer might prefer a "
 #~ "specially compiled binary, which is smaller in size, more optimized and "
diff --git a/weblate/zh_TW.po b/weblate/zh_TW.po
index bd99439115..097b42ed2a 100644
--- a/weblate/zh_TW.po
+++ b/weblate/zh_TW.po
@@ -13,7 +13,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Godot Engine latest\n"
 "Report-Msgid-Bugs-To: https://github.com/godotengine/godot-docs-l10n\n"
-"POT-Creation-Date: 2018-11-20 12:09+0100\n"
+"POT-Creation-Date: 2018-12-04 23:31+0100\n"
 "PO-Revision-Date: 2018-11-18 17:07+0000\n"
 "Last-Translator: ken l <macauhome@gmail.com>\n"
 "Language-Team: Chinese (Traditional) <https://hosted.weblate.org/projects/"
@@ -72,13 +72,14 @@ msgstr ""
 "容，請告知我們來讓文件變的更好！"
 
 #: ../../docs/index.rst:29
+#, fuzzy
 msgid ""
 "Submit an issue or pull request on the `GitHub repository <https://github."
 "com/godotengine/godot-docs/issues>`_, help us `translate the documentation "
 "<https://hosted.weblate.org/engage/godot-engine/>`_ into your language, or "
-"discuss with us on either the ``#documentation`` channel on `Discord "
-"<https://discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc."
-"freenode.net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
+"talk to us on either the ``#documentation`` channel on `Discord <https://"
+"discord.gg/zH7NUgz>`_, or the ``#godotengine-doc`` channel on `irc.freenode."
+"net <http://webchat.freenode.net/?channels=#godotengine-doc>`_!"
 msgstr ""
 "在`GitHub 儲存庫<https://github.com/godotengine/godot-docs/issues>`_提交問題"
 "或pull request，幫助我們`將文件 <https://hosted.weblate.org/engage/godot-"
@@ -149,7 +150,6 @@ msgstr "關於"
 #: ../../docs/tutorials/3d/high_dynamic_range.rst:7
 #: ../../docs/tutorials/3d/using_gridmaps.rst:7
 #: ../../docs/tutorials/3d/using_multi_mesh_instance.rst:7
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/audio/audio_buses.rst:7
 #: ../../docs/tutorials/audio/audio_streams.rst:7
 #: ../../docs/tutorials/physics/using_kinematic_body_2d.rst:7
@@ -168,6 +168,7 @@ msgstr "關於"
 #: ../../docs/tutorials/shading/shader_materials.rst:7
 #: ../../docs/tutorials/shading/screen-reading_shaders.rst:7
 #: ../../docs/tutorials/shading/migrating_to_godot_shader_language.rst:7
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:7
 #: ../../docs/tutorials/networking/ssl_certificates.rst:7
 #: ../../docs/tutorials/assetlib/uploading_to_assetlib.rst:7
 #: ../../docs/tutorials/vr/vr_starter_tutorial.rst:7
@@ -355,10 +356,11 @@ msgstr ""
 "+ 模組的開發、或編輯器插件等等的資訊。"
 
 #: ../../docs/about/introduction.rst:85
+#, fuzzy
 msgid ""
-"The :ref:`sec-community` gives information related to contributing to the "
-"engine development and the life of its community, e.g. how to report bugs, "
-"help with the documentation, etc. It also points to various community "
+"The :ref:`sec-community` section gives information related to contributing "
+"to the engine development and the life of its community, e.g. how to report "
+"bugs, help with the documentation, etc. It also points to various community "
 "channels like IRC and Discord and contains a list of recommended third-party "
 "tutorials outside of this documentation."
 msgstr ""
@@ -1406,7 +1408,7 @@ msgid "It can be extended (to have more functions)."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:39
-msgid "It can be added to other nodes as a child."
+msgid "It can be added to another node as a child."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scenes_and_nodes.rst:43
@@ -1873,7 +1875,7 @@ msgid ""
 "Designing based on scenes replaces that approach and makes development much "
 "faster and more straightforward, allowing you to concentrate on the game "
 "logic itself. Because most game components map directly to a scene, using a "
-"design-based on scene instantiation means little other architectural code is "
+"design based on scene instantiation means little other architectural code is "
 "needed."
 msgstr ""
 
@@ -1948,13 +1950,13 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:13
 msgid ""
-"This is great, mostly due the large amount of flexibility provided, but it "
-"also makes our work supporting languages more difficult."
+"This is great, mostly due to the large amount of flexibility provided, but "
+"it also makes our work supporting languages more difficult."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:16
 msgid ""
-"The \"Main\" languages in Godot, though, are GDScript and VisualScript. The "
+"The \"main\" languages in Godot, though, are GDScript and VisualScript. The "
 "main reason to choose them is their level of integration with Godot, as this "
 "makes the experience smoother; both have slick editor integration, while C# "
 "and C++ need to be edited in a separate IDE. If you are a big fan of "
@@ -2198,8 +2200,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:139
 msgid ""
-"In GDScript the file itself represents the class, so the class name field is "
-"not editable."
+"In GDScript, the file itself represents the class, so the class name field "
+"is not editable."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:142
@@ -2223,7 +2225,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:156
 msgid ""
 "To edit the script, select either of these buttons, both of which are "
-"highlighted in the above image. This will bring you to the script editor "
+"highlighted in the above image. This will bring you to the script editor, "
 "where a default template will be included:"
 msgstr ""
 
@@ -2297,7 +2299,7 @@ msgid ""
 "The top-left section displays a list of your scene's nodes with the emitting "
 "node's name highlighted in red. Select the \"Panel\" node here. When you "
 "select a node, the NodePath at the bottom will automatically update to point "
-"a relative path from the emitting node to the selected node."
+"to a relative path from the emitting node to the selected node."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/scripting.rst:210
@@ -2311,7 +2313,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/scripting.rst:215
 msgid ""
 "And that concludes the guide on how to use the visual interface. However, "
-"this is a scripting tutorial, so for the sake of learning, let's dive in to "
+"this is a scripting tutorial, so for the sake of learning, let's dive into "
 "the manual process!"
 msgstr ""
 
@@ -2651,6 +2653,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1458
 #: ../../docs/getting_started/scripting/gdscript/gdscript_styleguide.rst:183
 #: ../../docs/getting_started/scripting/visual_script/nodes_purposes.rst:164
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:679
 #: ../../docs/development/cpp/object_class.rst:211
 msgid "Signals"
 msgstr "信號"
@@ -3121,7 +3124,7 @@ msgstr ""
 msgid ""
 "Now we can use the ``_process()`` function to define what the player will "
 "do. ``_process()`` is called every frame, so we'll use it to update elements "
-"of our game which we expect will change often. Here we'll make it:"
+"of our game, which we expect will change often. Here we'll make it:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:202
@@ -3247,7 +3250,7 @@ msgstr ""
 msgid ""
 "Play the scene again and check that the animations are correct in each of "
 "the directions. When you're sure the movement is working correctly, add this "
-"line to ``_ready()`` so the player will be hidden when the game starts:"
+"line to ``_ready()``, so the player will be hidden when the game starts:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:387
@@ -3457,7 +3460,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:617
 msgid ""
-"Now add the following nodes as children of ``Main``, and name them as shown "
+"Now, add the following nodes as children of ``Main``, and name them as shown "
 "(values are in seconds):"
 msgstr ""
 
@@ -3555,7 +3558,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:667
 msgid ""
-"Add a script to ``Main``. At the top of the script we use ``export "
+"Add a script to ``Main``. At the top of the script, we use ``export "
 "(PackedScene)`` to allow us to choose the Mob scene we want to instance."
 msgstr ""
 
@@ -3583,7 +3586,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/your_first_game.rst:782
 msgid ""
-"In ``_on_MobTimer_timeout()`` we will create a mob instance, pick a random "
+"In ``_on_MobTimer_timeout()``, we will create a mob instance, pick a random "
 "starting location along the ``Path2D``, and set the mob in motion. The "
 "``PathFollow2D`` node will automatically rotate as it follows the path, so "
 "we will use that to select the mob's direction as well as its position."
@@ -4082,7 +4085,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:122
 #: ../../docs/getting_started/workflow/export/exporting_projects.rst:92
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:197
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:198
 #: ../../docs/development/compiling/compiling_with_mono.rst:126
 msgid "Export templates"
 msgstr ""
@@ -4139,8 +4142,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:156
 msgid ""
-"In the \"Resources\" and \"Features\" tabs you can customize how the game is "
-"exported for each platform. We can leave those settings alone for now."
+"In the \"Resources\" and \"Features\" tabs, you can customize how the game "
+"is exported for each platform. We can leave those settings alone for now."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:160
@@ -4216,7 +4219,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/exporting.rst:203
 msgid ""
-"Next, create a debug keystore with by running the following command on your "
+"Next, create a debug keystore by running the following command on your "
 "system's command line:"
 msgstr ""
 
@@ -4313,7 +4316,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/exporting.rst:273
 msgid ""
 "Viewing the `.html` file in your browser lets you play the game. However, "
-"you can't open the file directly, it neds to be served by a web server. If "
+"you can't open the file directly, it needs to be served by a web server. If "
 "you don't have one set up on your computer, you can use Google to find "
 "suggestions for your specific OS."
 msgstr ""
@@ -4399,14 +4402,14 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:38
 msgid ""
 "A Godot scene could be a Weapon, a Character, an Item, a Door, a Level, part "
-"of a level… anything you’d like. It works like a class in pure code except "
+"of a level… anything you’d like. It works like a class in pure code, except "
 "you’re free to design it by using the editor, using only the code, or mixing "
 "and matching the two."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:43
 msgid ""
-"It’s different from prefabs you find in several 3D engines as you can then "
+"It’s different from prefabs you find in several 3D engines, as you can then "
 "inherit from and extend those scenes. You may create a Magician that extends "
 "your Character. Modify the Character in the editor and the Magician will "
 "update as well. It helps you build your projects so that their structure "
@@ -4515,7 +4518,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:120
 msgid ""
 "On the other hand, an open codebase means you can **learn from and extend "
-"the engine** to your heart’s content. You can also debug games easily as "
+"the engine** to your heart’s content. You can also debug games easily, as "
 "Godot will print errors with a stack trace, even if they come from the "
 "engine itself."
 msgstr ""
@@ -4561,7 +4564,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/godot_design_philosophy.rst:151
 msgid ""
-"This leads to a reliable and flexible UI system as it powers the editor "
+"This leads to a reliable and flexible UI system, as it powers the editor "
 "itself. With the ``tool`` keyword, you can run any game code in the editor."
 msgstr ""
 
@@ -4601,7 +4604,7 @@ msgid ""
 "Computer displays, mobile phones, and TV screen come in all shapes and "
 "sizes. To ship a game, you'll need to support different screen ratios and "
 "resolutions. It can be hard to build responsive interfaces that adapt to all "
-"platforms. Thankfully, Godot comes with robust tools to design and manage "
+"platforms. Thankfully, Godot comes with robust tools to design and manage a "
 "responsive User Interface. To design your UI, you'll use the Control nodes. "
 "These are the nodes with green icons in the editor. There are dozens of "
 "them, to create anything from life bars to complex applications. Godot's "
@@ -4642,9 +4645,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:30
 msgid ""
 "Only use Control nodes when you design your interfaces. They have unique "
-"properties that allow them to work with one another. Other nodes like "
+"properties that allow them to work with one another. Other nodes, like "
 "Node2D, Sprite, etc. will not work. You can still use some nodes that work "
-"with others like the AnimationPlayer, Tween or the StreamPlayer. Control "
+"with others, like the AnimationPlayer, Tween or the StreamPlayer. Control "
 "nodes are CanvasItems like Node2D, so you can apply shaders to them."
 msgstr ""
 
@@ -4732,7 +4735,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:74
 msgid ""
 "**TextureRect** displays a texture or image inside a UI. It seems similar to "
-"the Sprite node but it offers multiple scaling modes. Set the Stretch Mode "
+"the Sprite node, but it offers multiple scaling modes. Set the Stretch Mode "
 "property to change its behavior:"
 msgstr ""
 
@@ -4849,7 +4852,7 @@ msgid ""
 "Label section, in the Inspector. Write the text in the ``Text`` property, "
 "and check Autowrap if you want it to respect the textbox's size. If Autowrap "
 "is off, you won't be able to scale the node. You can align the text "
-"horizontally and vertically with Align and Valign respectively."
+"horizontally and vertically with Align and Valign, respectively."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:152
@@ -4897,7 +4900,7 @@ msgstr ""
 msgid ""
 "The two approaches are not always compatible. Because a container controls "
 "its children, you cannot use the layout menu on them. Each container has a "
-"specific effect so you may need to nest several of them to get a working "
+"specific effect, so you may need to nest several of them to get a working "
 "interface. With the layout approach you work from the bottom up, on the "
 "children. As you don't insert extra containers in the scene it can make for "
 "cleaner hierarchies, but it's harder to arrange items in a row, column, "
@@ -5039,7 +5042,7 @@ msgid ""
 "Containers automatically arrange all children Control nodes including other "
 "containers in rows, columns, and more. Use them to add padding around your "
 "interface or center nodes in their bounding rectangles. All built-in "
-"containers update in the editor so you can see the effect instantly."
+"containers update in the editor, so you can see the effect instantly."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:281
@@ -5147,7 +5150,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_introduction_to_the_ui_system.rst:350
 msgid ""
 "Godot's UI system is complex, and has a lot more to offer. To learn how to "
-"design more advanced interface, head to the :ref:`GUI section <toc-learn-"
+"design more advanced interfaces, head to the :ref:`GUI section <toc-learn-"
 "features-gui>` of the docs."
 msgstr ""
 
@@ -5171,7 +5174,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:12
 msgid ""
-"You will learn how to design game UI efficiently, and how to use Godot's "
+"You will learn how to design game UIs efficiently, and how to use Godot's "
 "Control nodes. This page focuses on the visual part: everything you do from "
 "the editor. To learn how to code a life bar, read :doc:`ui_code_a_life_bar`"
 msgstr ""
@@ -5498,9 +5501,10 @@ msgid ""
 "To center the characters on the right, we'll use a ``CenterContainer``.  Add "
 "a ``CenterContainer`` node as a child of the ``HBoxContainer``. Then in the "
 "Inspector, scroll down to the ``Size Flags`` category and click on the field "
-"to the right of the ``Vertical`` property, and check ``Expand``. Do the same "
-"for the ``Horizontal`` property. Finally drag and drop the Characters into "
-"the ``CenterContainer``. The Characters element will center automatically."
+"to the right of the ``Vertical`` property, and check ``Expand`` in addition "
+"to ``Fill``. Do the same for the ``Horizontal`` property. Finally drag and "
+"drop the Characters into the ``CenterContainer``. The Characters element "
+"will center automatically."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:228
@@ -5530,8 +5534,9 @@ msgid ""
 "expand to take as much vertical space as possible. Select the "
 "``MenuOptions`` node. In the Inspector, scroll down to the ``Size Flags`` "
 "category. Click on the field to the right of the ``Vertical`` property, and "
-"check ``Expand``. The container expands to take all the available vertical "
-"space. But it respects its neighbors, the ``Logo`` and ``Version`` elements."
+"check ``Expand`` in addition to ``Fill``. The container expands to take all "
+"the available vertical space. But it respects its neighbors, the ``Logo`` "
+"and ``Version`` elements."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:252
@@ -5571,8 +5576,8 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_main_menu.rst:279
 msgid ""
-"Responsive User Interface is all about making sure our UIs scale well on all "
-"screen types. TV screens and computer displays have different sizes and "
+"A responsive User Interface is all about making sure our UIs scale well on "
+"all screen types. TV screens and computer displays have different sizes and "
 "ratios. In Godot, we use containers to control the position and the size of "
 "UI elements."
 msgstr ""
@@ -6474,7 +6479,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:9
 msgid ""
-"In this tutorial you will connect a character to a life bar and animate the "
+"In this tutorial, you will connect a character to a life bar and animate the "
 "health loss."
 msgstr ""
 
@@ -6543,9 +6548,9 @@ msgid ""
 "out some message. Other nodes can connect to the object that **emits** the "
 "signal and receive the information. It's a powerful tool we use a lot for "
 "User Interface and achievement systems. You don't want to use them "
-"everywhere though. Connecting two nodes adds some coupling between them. "
+"everywhere, though. Connecting two nodes adds some coupling between them. "
 "When there's a lot of connections, they become hard to manage. For more "
-"information on check out the `signals video tutorial <https://youtu.be/"
+"information, check out the `signals video tutorial <https://youtu.be/"
 "l0BkQxF7X3E>`_ on GDquest."
 msgstr ""
 
@@ -6562,12 +6567,12 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:58
 msgid ""
-"Load the ``start`` project in Godot. In the ``FileSystem`` dock double click "
-"on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 characters "
-"face each other. The pink enemy attacks and damages the green square at "
-"regular time intervals, until its death. Feel free to try out the game: the "
-"basic combat mechanics already work. But as the character isn't connected to "
-"the life bar the ``GUI`` doesn't do anything."
+"Load the ``start`` project in Godot. In the ``FileSystem`` dock, double "
+"click on LevelMockup.tscn to open it. It's an RPG game's mockup where 2 "
+"characters face each other. The pink enemy attacks and damages the green "
+"square at regular time intervals, until its death. Feel free to try out the "
+"game: the basic combat mechanics already work. But as the character isn't "
+"connected to the life bar, the ``GUI`` doesn't do anything."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:68
@@ -6590,8 +6595,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:77
 msgid ""
-"The GUI scene encapsulates all of the Game User Interface. It comes with a "
-"barebones script where we get the path to nodes that exist inside the scene:"
+"The GUI scene encapsulates all of the game's Graphical User Interface. It "
+"comes with a barebones script where we get the path to nodes that exist "
+"inside the scene:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:105
@@ -6767,10 +6773,10 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:219
 msgid ""
-"With this in mind let's connect the ``GUI`` to the ``Player``. Click on the "
+"With this in mind, let's connect the ``GUI`` to the ``Player``. Click on the "
 "``Player`` node in the scene dock to select it. Head down to the Inspector "
-"and click on the Node tab. This is the place to connect nodes to listen the "
-"one you selected."
+"and click on the Node tab. This is the place to connect nodes to listen to "
+"the one you selected."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:224
@@ -6849,16 +6855,16 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:274
 msgid ""
 "Inside the parens after the function name, add a ``player_health`` argument. "
-"When the player emits the ``health_changed`` signal it will send its current "
-"``health`` alongside it. Your code should look like:"
+"When the player emits the ``health_changed`` signal, it will send its "
+"current ``health`` alongside it. Your code should look like:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:292
 msgid ""
 "The engine does not convert PascalCase to snake_case, for C# examples we'll "
-"be using PascalCase for method names & camelCase for method parameters which "
-"follows the official `C# naming conventions. <https://docs.microsoft.com/en-"
-"us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
+"be using PascalCase for method names & camelCase for method parameters, "
+"which follows the official `C# naming conventions. <https://docs.microsoft."
+"com/en-us/dotnet/standard/design-guidelines/capitalization-conventions>`_"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:299
@@ -6869,7 +6875,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:302
 msgid ""
-"Inside ``_on_Player_health_changed`` let's call a second function called "
+"Inside ``_on_Player_health_changed``, let's call a second function called "
 "``update_health`` and pass it the ``player_health`` variable."
 msgstr ""
 
@@ -6911,7 +6917,7 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:350
 msgid ""
 "``str`` is a built-in function that converts about any value to text. "
-"``Number``'s ``text`` property requires a string so we can't assign it to "
+"``Number``'s ``text`` property requires a string, so we can't assign it to "
 "``new_value`` directly"
 msgstr ""
 
@@ -6938,7 +6944,7 @@ msgid ""
 "Our interface is functional, but it could use some animation. That's a good "
 "opportunity to introduce the ``Tween`` node, an essential tool to animate "
 "properties. ``Tween`` animates anything you'd like from a start to an end "
-"state over a certain duration. For example it can animate the health on the "
+"state over a certain duration. For example, it can animate the health on the "
 "``TextureProgress`` from its current level to the ``Player``'s new "
 "``health`` when the character takes damage."
 msgstr ""
@@ -7087,7 +7093,7 @@ msgid ""
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:531
-msgid "The animation is smooth but the number is broken"
+msgid "The animation is smooth, but the number is broken"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:533
@@ -7102,7 +7108,7 @@ msgid "Try the game again to see a nice blocky animation."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:559
-msgid "By rounding out animated\\_health we hit two birds with one stone"
+msgid "By rounding out animated\\_health, we kill two birds with one stone"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:563
@@ -7180,7 +7186,7 @@ msgstr ""
 msgid ""
 "``modulate`` takes a ``Color`` value with 4 channels: red, green, blue and "
 "alpha. If we darken any of the first three channels it darkens the "
-"interface. If we lower the alpha channel our interface fades out."
+"interface. If we lower the alpha channel, our interface fades out."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:615
@@ -7207,7 +7213,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/ui_code_a_life_bar.rst:654
 msgid ""
-"This time we change the ``modulate`` property and have it animate from "
+"This time, we change the ``modulate`` property and have it animate from "
 "``start_color`` to the ``end_color``. The duration is of one second, with a "
 "linear transition. Here again, because the transition is linear, the easing "
 "does not matter. Here's the complete ``_on_Player_died`` method:"
@@ -7344,9 +7350,9 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:38
 msgid ""
-"Now that we have an animation the property editor enters \"animation editing"
+"Now that we have an animation, the property editor enters \"animation editing"
 "\" mode. In this mode, a key icon appears next to every property of the "
-"property editor. In Godot any property of an object can be animated:"
+"property editor. In Godot, any property of an object can be animated:"
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/animations.rst:46
@@ -7415,16 +7421,16 @@ msgstr ""
 msgid ""
 "Up to this tutorial, we focused on the :ref:`Node <class_Node>` class in "
 "Godot as that's the one you use to code behavior and most of the engine's "
-"features rely on them. There is another datatype that is just as important: :"
+"features rely on it. There is another datatype that is just as important: :"
 "ref:`Resource <class_Resource>`."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:15
 msgid ""
 "*Nodes* give you functionality: they draw sprites, 3D models, simulate "
-"physics, arrange user interface, etc. **Resources** are **data containers**. "
-"They don't do anything on their own: instead nodes use the data contained in "
-"resources."
+"physics, arrange user interfaces, etc. **Resources** are **data "
+"containers**. They don't do anything on their own: instead, nodes use the "
+"data contained in resources."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:19
@@ -7441,14 +7447,14 @@ msgstr ""
 msgid ""
 "When the engine loads a resource from disk, **it only loads it once**. If a "
 "copy of that resource is already in memory, trying to load the resource "
-"again will return the same copy every time. As resources only contain data "
+"again will return the same copy every time. As resources only contain data, "
 "there is no need to duplicate them."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:31
 msgid ""
 "Every object, be it a Node or a Resource, can export properties. There are "
-"many types of Properties like String, integer, Vector2, etc., and any of "
+"many types of Properties, like String, integer, Vector2, etc., and any of "
 "these types can become a resource. This means that both nodes and resources "
 "can contain resources as properties:"
 msgstr ""
@@ -7479,16 +7485,16 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:51
 msgid ""
-"Clicking the resource preview allows us to view and edit the resources "
+"Clicking the resource preview allows us to view and edit the resource's "
 "properties."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:55
 msgid ""
-"The path property tells us where the resource comes from. In this case it "
+"The path property tells us where the resource comes from. In this case, it "
 "comes from a PNG image called ``robi.png``. When the resource comes from a "
 "file like this, it is an external resource. If you erase the path or this "
-"path is empty, it becomes built-in resource."
+"path is empty, it becomes a built-in resource."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:60
@@ -7550,7 +7556,7 @@ msgid ""
 "The approach has several advantages. As the :ref:`PackedScene.instance() "
 "<class_PackedScene_instance>` function is pretty fast, you can create new "
 "enemies, bullets, effects, etc. without having to load them again from disk "
-"each time. Remember that as always, images, meshes, etc. are all shared "
+"each time. Remember that, as always, images, meshes, etc. are all shared "
 "between the scene instances."
 msgstr ""
 
@@ -7580,7 +7586,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:158
 msgid ""
-"This comes with many distinct advantages over alternative data structures "
+"This comes with many distinct advantages over alternative data structures, "
 "such as JSON, CSV, or custom TXT files. Users can only import these assets "
 "as a :ref:`Dictionary <class_Dictionary>` (JSON) or as a :ref:`File "
 "<class_File>` to parse. What sets Resources apart is their inheritance of :"
@@ -7726,7 +7732,7 @@ msgstr ""
 
 #: ../../docs/getting_started/step_by_step/resources.rst:352
 msgid ""
-"CurveTables are the same thing except mapped to an Array of float values or "
+"CurveTables are the same thing, except mapped to an Array of float values or "
 "a :ref:`Curve <class_Curve>`/:ref:`Curve2D <class_Curve2D>` resource object."
 msgstr ""
 
@@ -7756,7 +7762,7 @@ msgid ""
 "File systems are yet another hot topic in engine development. The file "
 "system manages how the assets are stored and how they are accessed. A well-"
 "designed file system also allows multiple developers to edit the same source "
-"files and assets while collaborating together."
+"files and assets while collaborating."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/filesystem.rst:14
@@ -7788,7 +7794,7 @@ msgstr ""
 msgid ""
 "In general, the Godot file system avoids using metadata files. The reason "
 "for this is simple, existing asset managers and VCSs are simply much better "
-"than anything we can implement, so Godot tries the best to play along with "
+"than anything we can implement, so Godot tries its best to play along with "
 "SVN, Git, Mercurial, Perforce, etc."
 msgstr ""
 
@@ -8223,9 +8229,9 @@ msgstr ""
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:53
 msgid ""
 "Here you can add any number of scenes or scripts. Each entry in the list "
-"requires a name, which assigned as the node's ``name`` property. The order "
-"of the entries as they added to the global scene tree can be manipulated "
-"using the up/down arrow keys."
+"requires a name, which is assigned as the node's ``name`` property. The "
+"order of the entries as they are added to the global scene tree can be "
+"manipulated using the up/down arrow keys."
 msgstr ""
 
 #: ../../docs/getting_started/step_by_step/singletons_autoload.rst:60
@@ -8535,7 +8541,7 @@ msgid ""
 "surface. Both let you organize the project using the filesystem, but Godot's "
 "approach is simpler with a single configuration file, minimalist text "
 "format, and no metadata. All this contributes to Godot being much friendlier "
-"to VCS systems such as Git, Subversion, or Mercurial."
+"to VCS systems, such as Git, Subversion, or Mercurial."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:62
@@ -8615,7 +8621,7 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:95
 msgid ""
-"Godot's scene system is different: it actually consists in a tree made of "
+"Godot's scene system is different: it actually consists of a tree made of "
 "nodes. Each node serves a purpose: Sprite, Mesh, Light, etc. Basically, this "
 "is similar to the Unity scene system. However, each node can have multiple "
 "children, which makes each a subscene of the main scene. This means you can "
@@ -8732,12 +8738,12 @@ msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:148
 msgid ""
-"Second, it allows the extraction a subtree of the scene to make it a scene "
-"of its own, which answers the second and third questions: even if a scene "
-"tree gets too deep, it can be split into smaller subtrees. This also allows "
-"a better solution for reusability, as you can include any subtree as a child "
-"of any node. Putting multiple nodes in an empty GameObject in Unity does not "
-"provide the same possibility, apart from a visual organization."
+"Second, it allows the extraction of a subtree of the scene to make it a "
+"scene of its own, which answers the second and third questions: even if a "
+"scene tree gets too deep, it can be split into smaller subtrees. This also "
+"allows a better solution for reusability, as you can include any subtree as "
+"a child of any node. Putting multiple nodes in an empty GameObject in Unity "
+"does not provide the same possibility, apart from a visual organization."
 msgstr ""
 
 #: ../../docs/getting_started/editor/unity_to_godot.rst:151
@@ -8789,7 +8795,7 @@ msgstr ""
 #: ../../docs/getting_started/editor/unity_to_godot.rst:177
 msgid ""
 "Godot does not provide prefabs as such, but this functionality is here, "
-"again, filled thanks to its scene system: As we saw the scene system is "
+"again, filled thanks to its scene system: As we saw, the scene system is "
 "organized as a tree. Godot allows you to save a subtree of a scene as its "
 "own scene, thus saved into its own file. This new scene can then be "
 "instanced as many times as you want. Any change you make to this new, "
@@ -10226,7 +10232,7 @@ msgstr ""
 msgid ""
 "GDScript arrays are allocated linearly in memory for speed. Large arrays "
 "(more than tens of thousands of elements) may however cause memory "
-"fragmentation. If this is a concern special types of arrays are available. "
+"fragmentation. If this is a concern, special types of arrays are available. "
 "These only accept a single data type. They avoid memory fragmentation and "
 "also use less memory but are atomic and tend to run slower than generic "
 "arrays. They are therefore only recommended to use for large data sets:"
@@ -10606,7 +10612,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:869
 msgid ""
-"Remove any ``break``'s. If you don't want to ``break`` by default you can "
+"Remove any ``break``s. If you don't want to ``break`` by default, you can "
 "use ``continue`` for a fallthrough."
 msgstr ""
 
@@ -10685,7 +10691,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:935
 msgid ""
 "The length of the array is tested first, it has to be the same size as the "
-"pattern, otherwise the pattern don't match."
+"pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:937
@@ -10711,7 +10717,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:954
 msgid ""
 "The size of the dictionary is tested first, it has to be the same size as "
-"the pattern, otherwise the pattern don't match."
+"the pattern, otherwise the pattern doesn't match."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:956
@@ -10923,9 +10929,9 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1212
 msgid ""
 "One of the fundamental benefits of exporting member variables is to have "
-"them visible and editable in the editor. This way artists and game designers "
-"can modify values that later influence how the program runs. For this, a "
-"special export syntax is provided."
+"them visible and editable in the editor. This way, artists and game "
+"designers can modify values that later influence how the program runs. For "
+"this, a special export syntax is provided."
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1298
@@ -10970,7 +10976,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1333
 msgid ""
-"Exporting arrays works but with an important caveat: While regular arrays "
+"Exporting arrays works, but with an important caveat: While regular arrays "
 "are created local to every class instance, exported arrays are *shared* "
 "between all instances. This means that editing them in one instance will "
 "cause them to change in all other instances. Exported arrays can have "
@@ -11016,7 +11022,7 @@ msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1411
 msgid ""
-"As said *local* access will *not* trigger the setter and getter. Here is an "
+"As said, *local* access will *not* trigger the setter and getter. Here is an "
 "illustration of this:"
 msgstr ""
 
@@ -11027,7 +11033,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1428
 msgid ""
 "Scripts, by default, don't run inside the editor and only the exported "
-"properties can be changed. In some cases it is desired that they do run "
+"properties can be changed. In some cases, it is desired that they do run "
 "inside the editor (as long as they don't execute game code or manually avoid "
 "doing so). For this, the ``tool`` keyword exists and must be placed at the "
 "top of the file:"
@@ -11098,7 +11104,7 @@ msgid ""
 "immediately return from the current function, with the current frozen state "
 "of the same function as the return value. Calling ``resume`` on this "
 "resulting object will continue execution and return whatever the function "
-"returns. Once resumed the state object becomes invalid. Here is an example:"
+"returns. Once resumed, the state object becomes invalid. Here is an example:"
 msgstr ""
 
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1542
@@ -11118,7 +11124,7 @@ msgstr ""
 #: ../../docs/getting_started/scripting/gdscript/gdscript_basics.rst:1577
 msgid ""
 "The real strength of using ``yield`` is when combined with signals. "
-"``yield`` can accept two parameters, an object and a signal. When the signal "
+"``yield`` can accept two arguments, an object and a signal. When the signal "
 "is received, execution will recommence. Here are some examples:"
 msgstr ""
 
@@ -19502,7 +19508,7 @@ msgid "Let's run again! This time, the rotation displays fine!"
 msgstr ""
 
 #: ../../docs/tutorials/2d/custom_drawing_in_2d.rst:469
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:132
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:133
 msgid "Tools"
 msgstr "工具"
 
@@ -22441,8 +22447,7 @@ msgstr ""
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:111
 msgid ""
 "Always make sure to set a shadow *Max Distance* according to what the scene "
-"needs. The closer the max distance, the higher quality they shadows will "
-"have."
+"needs. A lower maximum distance will result in better-looking shadows."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:114
@@ -22655,9 +22660,9 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:228
 msgid ""
-"This allocation strategy works for most games, but you may to use a separate "
-"one in some cases (as example, a top-down game where all lights are around "
-"the same size and quadrands may have all the same subdivision)."
+"This allocation strategy works for most games, but you may want to use a "
+"separate one in some cases (as example, a top-down game where all lights are "
+"around the same size and quadrants may have all the same subdivision)."
 msgstr ""
 
 #: ../../docs/tutorials/3d/lights_and_shadows.rst:232
@@ -24642,7 +24647,7 @@ msgid ":ref:`CSGMesh <class_CSGMesh>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:23
-msgid ":ref:`CSGCombiner <class_CSGcombiner>'"
+msgid ":ref:`CSGCombiner <class_CSGcombiner>`"
 msgstr ""
 
 #: ../../docs/tutorials/3d/csg_tools.rst:30
@@ -25373,437 +25378,6 @@ msgid ""
 "Then modify the ``_ready()`` function to look like this:"
 msgstr ""
 
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:4
-msgid "Vertex displacement with shaders"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:9
-msgid ""
-"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
-"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
-"a wide variety of effects, but most commonly it is used as a quick way to "
-"turn a flat plane into a simple terrain. Typically this is done using a "
-"heightmap, but in order to keep everything self contained, in this tutorial "
-"we will use noise in a shader. At the end of this tutorial we will have a "
-"deformed plane that looks like a miniature terrain complete with dynamic "
-"lighting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:18
-msgid "By reading this tutorial you should gain a basic understanding of:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:20
-msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:21
-msgid ""
-"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:22
-msgid ""
-"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
-"ref:`Mesh<class_MeshInstance>`"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:23
-msgid ""
-"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
-"the :ref:`Mesh<class_MeshInstance>` in realtime"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:24
-msgid "How to approximate normals from a height function"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:25
-msgid "How to use a light with a custom material"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:28
-msgid "The plane mesh"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:30
-msgid ""
-"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
-"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:35
-msgid ""
-"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
-"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
-"in the Inspector. This will bring up a list of :ref:"
-"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:41
-msgid ""
-"The button will change into a small image of a plane. Click on it to enter "
-"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:44
-msgid ""
-"Then, in the viewport, click in the upper left corner where it says "
-"[Perspective]. A menu will appear. In the middle of the menu are options for "
-"how to display the scene. Select 'Display Wireframe'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:50
-msgid "This will allow you to see the triangles making up the plane."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:54
-msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:58
-msgid ""
-"You can see that there are now way more triangles in the :ref:"
-"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
-"thus allow us to add more detail."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:65
-msgid "Shader magic"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:67
-msgid ""
-"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
-"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:69
-msgid ""
-"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
-"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:73
-msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:75
-msgid ""
-"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:79
-msgid ""
-"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
-"Godot's Shader editor."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:83
-msgid ""
-"Notice how it is throwing an error? This is because the shader editor "
-"reloads shaders on the fly automatically. The first thing Godot shaders need "
-"is a declaration of what type of shader they are. Accordingly, we set the "
-"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
-"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
-"run the light shader on this object."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:94
-msgid ""
-"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
-"should turn white. If you were to comment out the ``render_mode`` the plane "
-"would appear blue because it would pick up the sky colors."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:97
-msgid ""
-"Next we will define a vertex shader. The vertex shader determines where the "
-"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
-"We will be using it to offset the height of each vertex and make our flat "
-"plane appear like a little terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:101
-msgid "We define the vertex shader like so:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:109
-msgid ""
-"With nothing in the ``vertex`` function Godot will use its default vertex "
-"shader. We can easily start to make changes by adding a single line:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:118
-msgid "Adding this line you should get an image like the one below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:122
-msgid ""
-"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
-"increased. And we are passing the ``x`` and ``z`` components of the "
-"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
-"appearance across the ``x`` and ``z`` axis."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:126
-msgid ""
-"What we want to achieve is the look of little hills, after all ``cos`` and "
-"``sin`` already look kind of like hills. We do so by scaling the inputs to "
-"the ``cos`` and ``sin`` functions."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:137
-msgid ""
-"This looks better, but it is still too spiky. This is because ``cos`` and "
-"``sin`` output values between ``-1`` and ``1``, so the range of the output "
-"is much too high. We correct this by multiplying the result by ``0.5`` to "
-"reduce the size."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:148
-msgid ""
-"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
-"onto something more interesting."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:151
-msgid "Noise"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:153
-msgid ""
-"Noise is a very popular tool for procedural generation. Think of it as "
-"similar to the cosine function where you have repeating hills except with "
-"noise each hill has a different height. Understanding noise is not necessary "
-"for this tutorial. There is nothing wrong with simply copying and pasting "
-"the code below."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:158
-msgid ""
-"The first function we use to generate the noise is the ``hash`` function. It "
-"gives the random height for each of the hill tops."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:167
-msgid ""
-"You will find similar functions to this all over the internet. It is "
-"lovingly referred to as the 'one-liner hash function'. It works well for "
-"simple noise, but there are many better alternatives floating around as "
-"well. For this tutorial it will work fine."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:171
-msgid ""
-"Next we define the ``noise`` function. It smoothly interpolates between the "
-"random heights. Again, if this code seems daunting, do not worry, just copy "
-"paste and move on with the tutorial."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:185
-msgid ""
-"Lastly, to add detail we combine successive layers of noise using something "
-"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
-"together layers of noise with increase frequency and decreasing amplitude. "
-"To implement it we run over a for loop where we increase the frequency each "
-"level, decrease the amplitude, and calculate a new layer of noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:204
-msgid ""
-"We can now use this noise function in place of ``cos`` and ``sin`` in the "
-"previous section."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:213
-msgid ""
-"With the noise function in place we already have something that looks kind "
-"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:217
-msgid "Fragment shader"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:219
-msgid ""
-"The difference between a vertex shader and a fragment shader is that the "
-"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
-"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
-"most importantly, sets the ``ALBEDO`` color of the :ref:"
-"`Mesh<class_MeshInstance>`."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:223
-msgid ""
-"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
-"instead of the wireframe. Set the viewport back to 'Display Normal'."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:228
-msgid ""
-"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
-"fragment shader is coloring each pixel white, but if every pixel is white we "
-"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
-"based on the height calculated in the vertex shader. We do so by setting the "
-"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
-"the fragment shader to the calculated ``COLOR`` variable."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:245
-msgid ""
-"With this change we can see the detail of the :ref:"
-"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
-"`Mesh<class_MeshInstance>`'s wireframe."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:250
-#: ../../docs/tutorials/shading/shading_language.rst:405
-msgid "Uniforms"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:252
-msgid ""
-"Uniform variables allow you to pass data from the game into the shader. They "
-"can be very useful for controlling shader effects. Uniforms can be almost "
-"any datatype that can be used in the shader. To use a uniform you declare it "
-"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:257
-msgid "Lets make a uniform that changes the height of the terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:264
-msgid ""
-"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
-"set to ``0.5``. You can set uniforms from gdscript by calling the function "
-"``set_shader_param`` on the material corresponding to the shader. The value "
-"passed from gdscript takes precedence over the value used to initialize it "
-"in the shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:273
-msgid ""
-"Remember that the string passed into ``set_shader_param`` must match the "
-"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
-"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
-"we will use it to set the height value instead of arbitrarily multiplying by "
-"``0.5``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:282
-msgid ""
-"The terrain should look exactly the same, but now we have control over the "
-"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:287
-msgid "And here it is with ``height_scale`` set to ``0.2``:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:291
-msgid ""
-"Using uniforms we can even change the value every frame to animate the "
-"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
-"especially useful for simple animations."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:295
-msgid "Interacting with light"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:297
-msgid ""
-"As a final part of this tutorial lets try to set up the terrain to interact "
-"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
-"scene."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:303
-msgid ""
-"You should notice that nothing changes, this is because we set the "
-"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
-"remove that."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:313
-msgid ""
-"It looks slightly better now, you can see the light affecting the terrain, "
-"and it has turned blue as a result of the sky. The problem is the light is "
-"affecting the terrain as if it were a flat plane. This is because the light "
-"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
-"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
-"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
-"so the normals are no longer correct. To fix this we need to recalculate the "
-"normals in the shader. Godot makes this easy for us, all we have to do is "
-"calculate the new normal and set ``NORMAL`` to that value in the vertex "
-"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
-"calculations for us."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:322
-msgid ""
-"To calculate the normal from noise we are going to use a technique called "
-"'central differences'. This is used a lot, especially in places like "
-"shadertoy, to calculate normals in shaders. What we will do is calculate the "
-"noise at four points surrounding the vertex in the ``x`` and ``z`` "
-"directions and then calculate the slope at the vertex from that. After all a "
-"normal is just an indicator of the slope of the noise."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:328
-msgid "We calculate the normal with one line in the vertex shader."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:336
-msgid ""
-"The variable ``e`` just makes it easier to add and subtract the right value "
-"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
-"of detail of the normal."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:339
-msgid "With ``NORMAL`` calculated the terrain now looks like:"
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:343
-msgid ""
-"This still does not look how we want it to. The issue here is that the noise "
-"changes faster than the vertices do. So when we calculate the normal at the "
-"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
-"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
-"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
-"``subdivision`` set to ``100``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:351
-msgid ""
-"Now we can drag the light around and the lighting will update automatically."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:357
-msgid ""
-"If you zoom the camera out you can see that the :ref:"
-"`Mesh<class_MeshInstance>` now looks like a small terrain."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:361
-msgid ""
-"That is everything for this tutorial. Hopefully you understand the basics of "
-"vertex shaders in Godot. As a further exercise try changing the "
-"``height_scale`` from gdscript, try using different :ref:`Primitive "
-"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
-"``height``."
-msgstr ""
-
-#: ../../docs/tutorials/3d/vertex_displacement_with_shaders.rst:366
-msgid ""
-"For further information on how to use shaders in Godot you should check out "
-"the :ref:`doc_shading_language` page."
-msgstr ""
-
 #: ../../docs/tutorials/3d/fps_tutorial/index.rst:2
 msgid "FPS tutorial"
 msgstr ""
@@ -27569,7 +27143,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:451
 msgid ""
-"Why are we using a :ref:`Area <class_Area>` and not a :ref:`RigidBody "
+"Why are we using an :ref:`Area <class_Area>` and not a :ref:`RigidBody "
 "<class_RigidBody>`? The main reason we're not using a :ref:`RigidBody "
 "<class_RigidBody>` is because we do not want the bullet to interact with "
 "other :ref:`RigidBody <class_RigidBody>` nodes. By using an :ref:`Area "
@@ -27579,7 +27153,7 @@ msgstr ""
 
 #: ../../docs/tutorials/3d/fps_tutorial/part_two.rst:455
 msgid ""
-"Another reason is simply because it is easier to detect collisions with a :"
+"Another reason is simply because it is easier to detect collisions with an :"
 "ref:`Area <class_Area>`!"
 msgstr ""
 
@@ -42877,9 +42451,9 @@ msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:55
 msgid ""
-"We are assuming you are familiar with the basics of shading for this "
-"tutorial. Even if you aren't, all the code will still be provided so you "
-"should have no problem following along."
+"Basic familiarity with shading is recommended for this tutorial. However, "
+"even if you are new to shaders, all the code will be provided so you should "
+"have no problem following along."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:66
@@ -42929,9 +42503,9 @@ msgid ""
 "Notice the ugly seam that forms where the texture wraps around? This is "
 "because we are picking a color based on UV coordinates and UV coordinates do "
 "not wrap around the texture. This is a classic problem in 2D map projection. "
-"Gamedevs often have a 2-dimensional map they want to project onto a sphere "
-"but when it wraps around it has large seams. There is an elegant work around "
-"for this problem that we will illustrate in the next section."
+"Game developers often have a 2-dimensional map they want to project onto a "
+"sphere but when it wraps around it has large seams. There is an elegant work "
+"around for this problem that we will illustrate in the next section."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:101
@@ -42985,46 +42559,44 @@ msgstr ""
 msgid ""
 "Now that we can calculate the 3D position of the surface of the sphere we "
 "can use 3D noise to make the planet. We will be using this noise function "
-"directly from a `Shadertoy <https://www.shadertoy.com/view/4dffRH>`_:"
+"directly from a `Shadertoy <https://www.shadertoy.com/view/Xsl3Dl>`_:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:198
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:175
 msgid ""
-"All credit goes to the initial author Inigo Quilez. It is published with the "
+"All credit goes to the author, Inigo Quilez. It is published with the "
 "``MIT`` licence."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:200
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:177
 msgid ""
-"Now to use ``noised``, add the following to the    ``fragment`` function:"
+"Now to use ``noise``, add the following to the    ``fragment`` function:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:209
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:186
 msgid "In order to highlight the texture, we set the material to unshaded."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:211
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:188
 msgid ""
 "You can see now that the noise indeed wraps seamlessly around the sphere. "
 "Although this looks nothing like the planet you were promised. So lets move "
 "onto something more colorful."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:215
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:192
 msgid "Coloring the planet"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:217
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:194
 msgid ""
-"Now to make the planet colors. There are many ways to do this, if you look "
-"on `Shadertoy <https://www.shadertoy.com>`_ you will find all kinds of ways "
-"of mapping colors to procedural planet terrain. For now we will stick with a "
-"simple gradient between water and land."
+"Now to make the planet colors. While, there are many ways to do this, for "
+"now we will stick with a gradient between water and land."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:221
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:197
 msgid ""
-"To make a gradient in glsl we use the ``mix`` function. ``mix`` takes two "
+"To make a gradient in GLSL we use the ``mix`` function. ``mix`` takes two "
 "values to interpolate between and a third parameter to choose how much to "
 "interpolate between them, in essence it *mixes* the two values together. In "
 "other APIs this function is often called ``lerp``. Although, ``lerp`` is "
@@ -43032,7 +42604,7 @@ msgid ""
 "values whether it be floats or vector types."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:231
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:207
 msgid ""
 "The first color is blue for the ocean. The second color is a kind of reddish "
 "color (because all alien planets need red terrain). And finally they are "
@@ -43041,7 +42613,7 @@ msgid ""
 "Now you can see that the colors change between blue and red."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:238
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:214
 msgid ""
 "That is a little more blurry than we want. Planets typically have a "
 "relatively clear separation between land and sea. In order to do that we "
@@ -43049,7 +42621,7 @@ msgid ""
 "whole line becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:246
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:222
 msgid ""
 "What ``smoothstep`` does is return ``0`` if the third parameter is below the "
 "first and return 1 if the third parameter is larger than the second and "
@@ -43059,7 +42631,7 @@ msgid ""
 "``0``."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:253
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:229
 msgid ""
 "One more thing to make this a little more planet-y. The land shouldn't be so "
 "blobby lets make the edges a little rougher. A trick that is often used in "
@@ -43070,19 +42642,19 @@ msgid ""
 "with four lines of shader code instead of just one. ``n`` becomes:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:267
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:243
 msgid "And now the planet looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:271
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:247
 msgid "And with shading turned back on it looks like:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:252
 msgid "Making an ocean"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:278
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:254
 msgid ""
 "One final thing to make this look more like a planet. The ocean and the land "
 "reflect light differently. So we want the ocean to shine a little more than "
@@ -43090,13 +42662,13 @@ msgid ""
 "channel of our output ``COLOR`` and using it as a Roughness map."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:286
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:262
 msgid ""
 "This line returns ``0.3`` for water and ``1.0`` for land. This means that "
 "the land is going to be quite rough while the water will be quite smooth."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:265
 msgid ""
 "And then in the material under the \"Metallic\" section make sure "
 "``Metallic`` is set to ``0`` and ``Specular`` is set to ``1``. The reason "
@@ -43104,7 +42676,7 @@ msgid ""
 "values are not physically accurate, but they are good enough for this demo."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:269
 msgid ""
 "Next under the \"Roughness\" section set ``Roughness`` to ``1`` and set the "
 "roughness texture to a :ref:`Viewport Texture <class_ViewportTexture>` "
@@ -43113,7 +42685,7 @@ msgid ""
 "``alpha`` channel of our output ``COLOR`` as the ``Roughness`` value."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:300
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:276
 msgid ""
 "You'll notice that very little changes except that the planet is no longer "
 "reflecting the sky. This is happening because by default when something is "
@@ -43127,7 +42699,7 @@ msgid ""
 "object on top of another we want to enable ``blend_premul_alpha``:"
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:313
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:289
 msgid ""
 "This pre-multiplies the colors by the ``alpha`` value and then blends them "
 "correctly together. Typically when blending one transparent color on top of "
@@ -43136,7 +42708,7 @@ msgid ""
 "``blend_premul_alpha`` fixes that."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:317
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:293
 msgid ""
 "Now the planet should look like it is reflecting light on the ocean but not "
 "the land. If you haven't done so already, add an :ref:`OmniLight "
@@ -43144,10 +42716,10 @@ msgid ""
 "of the reflections on the ocean."
 msgstr ""
 
-#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:323
+#: ../../docs/tutorials/viewports/using_viewport_as_texture.rst:299
 msgid ""
-"And there you have it. A simple procedural planet generated using a :ref:"
-"`Viewport <class_Viewport>`."
+"And there you have it. A procedural planet generated using a :ref:`Viewport "
+"<class_Viewport>`."
 msgstr ""
 
 #: ../../docs/tutorials/viewports/custom_postprocessing.rst:4
@@ -44112,6 +43684,11 @@ msgid ""
 "default"
 msgstr ""
 
+#: ../../docs/tutorials/shading/shading_language.rst:405
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:250
+msgid "Uniforms"
+msgstr ""
+
 #: ../../docs/tutorials/shading/shading_language.rst:407
 msgid ""
 "Passing values to shaders is possible. These are global to the whole shader "
@@ -47027,6 +46604,432 @@ msgid ""
 "<glsl_coordinates>`."
 msgstr ""
 
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:4
+msgid "Vertex displacement with shaders"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:9
+msgid ""
+"This tutorial will teach you how to displace the vertices of a :ref:`Plane "
+"Mesh<class_PlaneMesh>` inside a shader. Vertex displacement can be used for "
+"a wide variety of effects, but most commonly it is used as a quick way to "
+"turn a flat plane into a simple terrain. Typically this is done using a "
+"heightmap, but in order to keep everything self contained, in this tutorial "
+"we will use noise in a shader. At the end of this tutorial we will have a "
+"deformed plane that looks like a miniature terrain complete with dynamic "
+"lighting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:18
+msgid "By reading this tutorial you should gain a basic understanding of:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:20
+msgid "How to create and subdivide a :ref:`Plane Mesh<class_PlaneMesh>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:21
+msgid ""
+"How to create and assign a material to a :ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:22
+msgid ""
+"How to write a :ref:`Shader<class_Shader>` that displaces the vertices of a :"
+"ref:`Mesh<class_MeshInstance>`"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:23
+msgid ""
+"How to pass values (Uniforms) into a :ref:`Shader<class_Shader>` to update "
+"the :ref:`Mesh<class_MeshInstance>` in realtime"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:24
+msgid "How to approximate normals from a height function"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:25
+msgid "How to use a light with a custom material"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:28
+msgid "The plane mesh"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:30
+msgid ""
+"First, add a :ref:`Spatial<class_Spatial>` node to the scene to act as the "
+"root. Next, add a :ref:`MeshInstance<class_MeshInstance>` as a child."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:35
+msgid ""
+"Select the newly created :ref:`MeshInstance<class_MeshInstance>`. Then click "
+"on the button that says \"null\" next to the :ref:`Mesh<class_MeshInstance>` "
+"in the Inspector. This will bring up a list of :ref:"
+"`PrimitiveMeshes<class_PrimitiveMesh>`. Select \"New PlaneMesh\"."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:41
+msgid ""
+"The button will change into a small image of a plane. Click on it to enter "
+"into the Inspector for the :ref:`Plane Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:44
+msgid ""
+"Then, in the viewport, click in the upper left corner where it says "
+"[Perspective]. A menu will appear. In the middle of the menu are options for "
+"how to display the scene. Select 'Display Wireframe'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:50
+msgid "This will allow you to see the triangles making up the plane."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:54
+msgid "Now set the ``Subdivide Width`` and ``Subdivide Height`` to ``32``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:58
+msgid ""
+"You can see that there are now way more triangles in the :ref:"
+"`Mesh<class_MeshInstance>`. This will give us more vertices to work with and "
+"thus allow us to add more detail."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:65
+msgid "Shader magic"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:67
+msgid ""
+"Now that we have a :ref:`Plane Mesh<class_MeshInstance>` to draw lets setup "
+"the material that will deform the :ref:`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:69
+msgid ""
+"Click beside material in the :ref:`Plane Mesh<class_MeshInstance>` Menu and "
+"create a new :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:73
+msgid "Then click on the created :ref:`ShaderMaterial<class_ShaderMaterial>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:75
+msgid ""
+"Then click beside 'shader' and create a new :ref:`Shader<class_Shader>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:79
+msgid ""
+"Click into the newly created :ref:`Shader<class_Shader>`. You should now see "
+"Godot's Shader editor."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:83
+msgid ""
+"Notice how it is throwing an error? This is because the shader editor "
+"reloads shaders on the fly automatically. The first thing Godot shaders need "
+"is a declaration of what type of shader they are. Accordingly, we set the "
+"variable ``shader_type`` to ``spatial``. One more thing we will add is the "
+"``render_mode``, we will set it to ``unshaded``. This means that Godot won't "
+"run the light shader on this object."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:94
+msgid ""
+"This should remove the errors and your :ref:`Mesh<class_MeshInstance>` "
+"should turn white. If you were to comment out the ``render_mode`` the plane "
+"would appear blue because it would pick up the sky colors."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:97
+msgid ""
+"Next we will define a vertex shader. The vertex shader determines where the "
+"vertices of your :ref:`Mesh<class_MeshInstance>` appear in the final scene. "
+"We will be using it to offset the height of each vertex and make our flat "
+"plane appear like a little terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:101
+msgid "We define the vertex shader like so:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:109
+msgid ""
+"With nothing in the ``vertex`` function Godot will use its default vertex "
+"shader. We can easily start to make changes by adding a single line:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:118
+msgid "Adding this line you should get an image like the one below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:122
+msgid ""
+"Okay, lets unpack this. The ``y`` value of the ``VERTEX`` is being "
+"increased. And we are passing the ``x`` and ``z`` components of the "
+"``VERTEX`` as arguments to ``cos`` and ``sin`` this gives us a wave like "
+"appearance across the ``x`` and ``z`` axis."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:126
+msgid ""
+"What we want to achieve is the look of little hills, after all ``cos`` and "
+"``sin`` already look kind of like hills. We do so by scaling the inputs to "
+"the ``cos`` and ``sin`` functions."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:137
+msgid ""
+"This looks better, but it is still too spiky. This is because ``cos`` and "
+"``sin`` output values between ``-1`` and ``1``, so the range of the output "
+"is much too high. We correct this by multiplying the result by ``0.5`` to "
+"reduce the size."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:148
+msgid ""
+"Looks much more hilly now. But ``cos`` and ``sin`` are boring. Lets move "
+"onto something more interesting."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:151
+msgid "Noise"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:153
+msgid ""
+"Noise is a very popular tool for procedural generation. Think of it as "
+"similar to the cosine function where you have repeating hills except with "
+"noise each hill has a different height. Understanding noise is not necessary "
+"for this tutorial. There is nothing wrong with simply copying and pasting "
+"the code below."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:158
+msgid ""
+"The first function we use to generate the noise is the ``hash`` function. It "
+"gives the random height for each of the hill tops."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:167
+msgid ""
+"You will find similar functions to this all over the internet. It is "
+"lovingly referred to as the 'one-liner hash function'. It works well for "
+"simple noise, but there are many better alternatives floating around as "
+"well. For this tutorial it will work fine."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:171
+msgid ""
+"Next we define the ``noise`` function. It smoothly interpolates between the "
+"random heights. Again, if this code seems daunting, do not worry, just copy "
+"paste and move on with the tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:185
+msgid ""
+"Lastly, to add detail we combine successive layers of noise using something "
+"called fractal brownian motion or FBM. Scary name aside FBM noise just adds "
+"together layers of noise with increase frequency and decreasing amplitude. "
+"To implement it we run over a for loop where we increase the frequency each "
+"level, decrease the amplitude, and calculate a new layer of noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:204
+msgid ""
+"We can now use this noise function in place of ``cos`` and ``sin`` in the "
+"previous section."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:213
+msgid ""
+"With the noise function in place we already have something that looks kind "
+"of cool. There is a lot of detail, it kind of looks hilly or mountainous."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:217
+msgid "Fragment shader"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:219
+msgid ""
+"The difference between a vertex shader and a fragment shader is that the "
+"vertex shader runs per vertex and sets properties such as ``VERTEX`` "
+"(position) and ``NORMAL``, while the fragment shader runs per pixel and, "
+"most importantly, sets the ``ALBEDO`` color of the :ref:"
+"`Mesh<class_MeshInstance>`."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:223
+msgid ""
+"Now lets look at the :ref:`Mesh<class_MeshInstance>` with a regular shader "
+"instead of the wireframe. Set the viewport back to 'Display Normal'."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:228
+msgid ""
+"The :ref:`Mesh<class_MeshInstance>` appears completely white because the "
+"fragment shader is coloring each pixel white, but if every pixel is white we "
+"lose detail on the :ref:`Mesh<class_MeshInstance>`. So lets color each pixel "
+"based on the height calculated in the vertex shader. We do so by setting the "
+"``COLOR`` variable in the vertex shader. And by setting the ``ALBEDO`` in "
+"the fragment shader to the calculated ``COLOR`` variable."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:245
+msgid ""
+"With this change we can see the detail of the :ref:"
+"`Mesh<class_MeshInstance>`, even without displaying the :ref:"
+"`Mesh<class_MeshInstance>`'s wireframe."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:252
+msgid ""
+"Uniform variables allow you to pass data from the game into the shader. They "
+"can be very useful for controlling shader effects. Uniforms can be almost "
+"any datatype that can be used in the shader. To use a uniform you declare it "
+"in your :ref:`Shader<class_Shader>` using the keyword ``uniform``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:257
+msgid "Lets make a uniform that changes the height of the terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:264
+msgid ""
+"Godot lets you initialize a uniform with a value, here ``height_scale`` is "
+"set to ``0.5``. You can set uniforms from gdscript by calling the function "
+"``set_shader_param`` on the material corresponding to the shader. The value "
+"passed from gdscript takes precedence over the value used to initialize it "
+"in the shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:273
+msgid ""
+"Remember that the string passed into ``set_shader_param`` must match the "
+"name of the uniform variable in the :ref:`Shader<class_Shader>`. You can use "
+"the uniform variable anywhere inside your :ref:`Shader<class_Shader>`. Here, "
+"we will use it to set the height value instead of arbitrarily multiplying by "
+"``0.5``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:282
+msgid ""
+"The terrain should look exactly the same, but now we have control over the "
+"height easily. Here is the same terrain with ``height_scale`` set to ``1``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:287
+msgid "And here it is with ``height_scale`` set to ``0.2``:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:291
+msgid ""
+"Using uniforms we can even change the value every frame to animate the "
+"height of the terrain. Combined with :ref:`Tweens<class_Tween>` this can be "
+"especially useful for simple animations."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:295
+msgid "Interacting with light"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:297
+msgid ""
+"As a final part of this tutorial lets try to set up the terrain to interact "
+"with light. First, we will add an :ref:`OmniLight<class_OmniLight>` to the "
+"scene."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:303
+msgid ""
+"You should notice that nothing changes, this is because we set the "
+"``render_mode`` to ``unshaded`` at the beginning of this tutorial, lets "
+"remove that."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:313
+msgid ""
+"It looks slightly better now, you can see the light affecting the terrain, "
+"and it has turned blue as a result of the sky. The problem is the light is "
+"affecting the terrain as if it were a flat plane. This is because the light "
+"shader uses the normals of the :ref:`Mesh<class_MeshInstance>` to calculate "
+"light. The normals are stored in the :ref:`Mesh<class_MeshInstance>`, but we "
+"are changing the shape of the :ref:`Mesh<class_MeshInstance>` in the shader "
+"so the normals are no longer correct. To fix this we need to recalculate the "
+"normals in the shader. Godot makes this easy for us, all we have to do is "
+"calculate the new normal and set ``NORMAL`` to that value in the vertex "
+"shader. With ``NORMAL`` set Godot will do all the difficult lighting "
+"calculations for us."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:322
+msgid ""
+"To calculate the normal from noise we are going to use a technique called "
+"'central differences'. This is used a lot, especially in places like "
+"shadertoy, to calculate normals in shaders. What we will do is calculate the "
+"noise at four points surrounding the vertex in the ``x`` and ``z`` "
+"directions and then calculate the slope at the vertex from that. After all a "
+"normal is just an indicator of the slope of the noise."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:328
+msgid "We calculate the normal with one line in the vertex shader."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:336
+msgid ""
+"The variable ``e`` just makes it easier to add and subtract the right value "
+"from the ``VERTEX``. Setting ``e`` to a lower number will increase the level "
+"of detail of the normal."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:339
+msgid "With ``NORMAL`` calculated the terrain now looks like:"
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:343
+msgid ""
+"This still does not look how we want it to. The issue here is that the noise "
+"changes faster than the vertices do. So when we calculate the normal at the "
+"point of the ``VERTEX`` it does not align with what we see in the final :ref:"
+"`Mesh<class_MeshInstance>`. In order to fix this we add more vertices. The "
+"below image is made with a :ref:`Mesh<class_MeshInstance>` with "
+"``subdivision`` set to ``100``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:351
+msgid ""
+"Now we can drag the light around and the lighting will update automatically."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:357
+msgid ""
+"If you zoom the camera out you can see that the :ref:"
+"`Mesh<class_MeshInstance>` now looks like a small terrain."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:361
+msgid ""
+"That is everything for this tutorial. Hopefully you understand the basics of "
+"vertex shaders in Godot. As a further exercise try changing the "
+"``height_scale`` from gdscript, try using different :ref:`Primitive "
+"Meshes<class_PrimitiveMesh>`, and try making your own functions to calculate "
+"``height``."
+msgstr ""
+
+#: ../../docs/tutorials/shading/vertex_displacement_with_shaders.rst:366
+msgid ""
+"For further information on how to use shaders in Godot you should check out "
+"the :ref:`doc_shading_language` page."
+msgstr ""
+
 #: ../../docs/tutorials/networking/index.rst:2
 msgid "Networking"
 msgstr ""
@@ -51571,11 +51574,11 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-c-example.rst:231
 #: ../../docs/development/compiling/index.rst:2
-#: ../../docs/development/compiling/compiling_for_windows.rst:87
-#: ../../docs/development/compiling/compiling_for_x11.rst:80
-#: ../../docs/development/compiling/compiling_for_osx.rst:19
-#: ../../docs/development/compiling/compiling_for_ios.rst:16
-#: ../../docs/development/compiling/compiling_for_uwp.rst:21
+#: ../../docs/development/compiling/compiling_for_windows.rst:90
+#: ../../docs/development/compiling/compiling_for_x11.rst:83
+#: ../../docs/development/compiling/compiling_for_osx.rst:22
+#: ../../docs/development/compiling/compiling_for_ios.rst:19
+#: ../../docs/development/compiling/compiling_for_uwp.rst:24
 msgid "Compiling"
 msgstr ""
 
@@ -51769,45 +51772,41 @@ msgstr ""
 
 #: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:18
 msgid ""
-"We'll be looking at NativeScript 1.0 which is available in Godot 3.0. Godot "
-"3.1 will see the introduction of NativeScript 1.1, which comes with a number "
-"of improvements. We'll update this tutorial once it is officially released, "
-"but the overall structure remains similar."
+"Godot 3.1 saw the introduction of the NativeScript 1.1 additions that "
+"enabled the GDNative team to build a nicer C++ bindings library. These "
+"changes have now been merged into the master branch and will be the way we "
+"go forward. If you want to write a C++ GDNative plugin that also supports "
+"Godot 3.0 you will need to use the 3.0 branch and the NativeScript 1.0 "
+"syntax. We'll be showing them side by side in this writeup."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:23
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:26
 msgid ""
 "You can download the full example we'll be creating in this tutorial `on "
 "GitHub <https://github.com/BastiaanOlij/gdnative_cpp_example>`_."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:27
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:30
 msgid "Setting up the project"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:29
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
 msgid "There are a few prerequisites you'll need:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:31
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
 msgid "a Godot 3.x executable,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:32
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
 msgid "a C++ compiler,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:33
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:36
 msgid "SCons as a build tool,"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:34
-msgid ""
-"a copy of the `godot_headers repository <https://github.com/GodotNativeTools/"
-"godot_headers>`_,"
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:35
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
 #, fuzzy
 msgid ""
 "a copy of the `godot-cpp repository <https://github.com/GodotNativeTools/"
@@ -51816,29 +51815,30 @@ msgstr ""
 "在這份文件之外，你可能也會想看看 `Godot 的 demo 專案 <https://github.com/"
 "godotengine/godot-demo-projects>`_。"
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:37
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:39
 msgid ""
 "See also :ref:`Compiling <toc-devel-compiling>` as the build tools are "
 "identical to the ones you need to compile Godot from source."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:40
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:42
 msgid ""
 "You can download these repositories from GitHub or let Git do the work for "
 "you. Note that these repositories now have different branches for different "
 "versions of Godot. GDNative modules written for an earlier version of Godot "
 "will work in newer versions (with the exception of one breaking change in "
 "ARVR interfaces between 3.0 and 3.1) but not vise versa so make sure you "
-"download the correct branch."
+"download the correct branch. Also note that the version of Godot you use to "
+"generate the ``api.json`` with becomes your minimum version."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:44
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:52
 msgid ""
 "If you are versioning your project using Git, it is a good idea to add them "
 "as Git submodules:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:58
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:74
 msgid ""
 "If you decide to just download the repositories or clone them into your "
 "project folder, make sure to keep the folder layout identical to the one "
@@ -51846,131 +51846,127 @@ msgid ""
 "project follows this layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:63
-msgid ""
-"Do make sure you clone recursive to pull in both repositories: .. code-"
-"block:: none"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:79
+msgid "Do make sure you clone recursive to pull in both repositories:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:66
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:94
 msgid ""
-"mkdir gdnative_cpp_example cd gdnative_cpp_example git clone --recursive -b "
-"3.0 https://github.com/GodotNativeTools/godot-cpp"
+"``godot-cpp`` now includes ``godot_headers`` as a nested submodule, if "
+"you've manually downloaded them please make sure to place ``godot_headers`` "
+"inside of the ``godot-cpp`` folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:70
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:96
 msgid ""
-"The ``-b 3.0`` I've added as an example to show how to select a specific "
-"branch for a specific version of Godot. Also ``godot-cpp`` now includes "
-"``godot_headers`` as a nested submodule, if you've manually downloaded them "
-"please make sure to place ``godot_headers`` inside of the ``godot-cpp`` "
-"folder."
-msgstr ""
-
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:73
-msgid ""
-"You don't have to do it this way but I've found it easiest to manage. If you "
-"decide to just download the repositories or just clone them into your "
-"folder, makes sure to keep the folder layout the same as I've setup here as "
+"You don't have to do it this way but we've found it easiest to manage. If "
+"you decide to just download the repositories or just clone them into your "
+"folder, make sure to keep the folder layout the same as we've setup here as "
 "much of the code we'll be showcasing here assumes the project has this "
 "layout."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:75
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:98
 msgid ""
 "If you cloned the example from the link specified in the introduction, the "
 "submodules are not automatically initialized. You will need to execute the "
 "following commands:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:84
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:107
 msgid "This will clone these two repositories into your project folder."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:87
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:110
 msgid "Building the C++ bindings"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:89
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:112
 msgid ""
 "Now that we've downloaded our prerequisites, it is time to build the C++ "
 "bindings."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:92
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:115
 msgid ""
 "The repository contains a copy of the metadata for the current Godot "
 "release, but if you need to build these bindings for a newer version of "
 "Godot, simply call the Godot executable:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:100
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
 msgid ""
 "Place the resulting ``api.json`` file in the project folder and add "
 "``use_custom_api_file=yes custom_api_file=../api.json`` to the scons command "
 "below."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:102
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:125
 msgid ""
 "To generate and compile the bindings, use this command (replacing "
 "``<platform>`` with ``windows``, ``x11`` or ``osx`` depending on your OS):"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:111
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:134
 msgid ""
 "This step will take a while. When it is completed, you should have static "
 "libraries that can be compiled into your project stored in ``godot-cpp/bin/"
 "``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:114
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:137
 msgid ""
 "At some point in the future, compiled binaries will be available, making "
 "this step optional."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:118
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:140
+msgid ""
+"You may need to add ``bits=64`` to the command on Windows. We're still "
+"working on better auto detection."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:143
 msgid "Creating a simple plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:120
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:145
 msgid ""
 "Now it's time to build an actual plugin. We'll start by creating an empty "
 "Godot project in which we'll place a few files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:123
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:148
 msgid ""
 "Open Godot and create a new project. For this example, we will place it in a "
 "folder called ``demo`` inside our GDNative module's folder structure."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:126
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:151
 msgid ""
 "In our demo project, we'll create a scene containing a Node called \"Main\" "
 "and we'll save it as ``main.tscn``. We'll come back to that later."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:129
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:154
 msgid ""
 "Back in the top-level GDNative module folder, we're also going to create a "
 "subfolder called ``src`` in which we'll place our source files."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:132
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:157
 msgid ""
 "You should now have ``demo``, ``godot-cpp``, ``godot_headers``, and ``src`` "
 "directories in your GDNative module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:135
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:160
 msgid ""
 "In the ``src`` folder, we'll start with creating our header file for the "
 "GDNative node we'll be creating. We will name it ``gdexample.h``:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:167
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:224
 msgid ""
 "There are a few things of note to the above. We're including ``Godot.hpp`` "
 "which contains all our basic definitions. After that, we include ``Sprite."
@@ -51978,55 +51974,55 @@ msgid ""
 "class in our module."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:172
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:229
 msgid ""
 "We're using the namespace ``godot``, since everything in GDNative is defined "
 "within this namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:175
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:232
 msgid ""
 "Then we have our class definition, which inherits from our Sprite through a "
-"container class. We'll see a few side effects of this later on. This is also "
-"the main bit that is going to improve in NativeScript 1.1. The "
+"container class. We'll see a few side effects of this later on. The "
 "``GODOT_CLASS`` macro sets up a few internal things for us."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:180
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
 msgid "After that, we declare a single member variable called ``time_passed``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:182
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:238
 msgid ""
 "In the next block we're defining our methods, we obviously have our "
 "constructor and destructor defined, but there are two other functions that "
-"will likely look familiar to some."
+"will likely look familiar to some, and one new method."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:186
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:242
 msgid ""
 "The first is ``_register_methods``, which is a static function that Godot "
 "will call to find out which methods can be called on our NativeScript and "
 "which properties it exposes. The second is our ``_process`` function, which "
 "will work exactly the same as the ``_process`` function you're used to in "
-"GDScript."
+"GDScript. The third is our ``_init`` function which is called after Godot "
+"has properly set up our object. It has to exist even if you don't place any "
+"code in it."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:192
-msgid ""
-"So, let's implement our functions by creating our ``gdexample.cpp`` file:"
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:251
+msgid "Let's implement our functions by creating our ``gdexample.cpp`` file:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:221
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:311
 msgid ""
 "This one should be straightforward. We're implementing each method of our "
 "class that we defined in our header file. Note that the ``register_method`` "
 "call **must** expose the ``_process`` method, otherwise Godot will not be "
-"able to use it. However, we do not have to tell Godot about our constructor "
-"and destructor."
+"able to use it. However, we do not have to tell Godot about our constructor, "
+"destructor and ``_init`` functions."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:227
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:317
 msgid ""
 "The other method of note is our ``_process`` function, which simply keeps "
 "track of how much time has passed and calculates a new position for our "
@@ -52037,22 +52033,22 @@ msgid ""
 "``set_position`` can be called directly on our class."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:236
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:326
 msgid ""
 "There is one more C++ file we need; we'll name it ``gdlibrary.cpp``. Our "
 "GDNative plugin can contain multiple NativeScripts, each with their own "
-"header and source file like we've implemented ``gdexample`` up above. What "
+"header and source file like we've implemented ``GDExample`` up above. What "
 "we need now is a small bit of code that tells Godot about all the "
 "NativeScripts in our GDNative plugin."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:260
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:350
 msgid ""
 "Note that we are not using the ``godot`` namespace here, since the three "
 "functions implemented here need to be defined without a namespace."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:263
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:353
 msgid ""
 "The ``godot_gdnative_init`` and ``godot_gdnative_terminate`` functions get "
 "called respectively when Godot loads our plugin and when it unloads it. All "
@@ -52061,7 +52057,7 @@ msgid ""
 "needs."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:269
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:359
 msgid ""
 "The important function is the third function called "
 "``godot_nativescript_init``. We first call a function in our bindings "
@@ -52069,11 +52065,11 @@ msgid ""
 "``register_class`` for each of our classes in our library."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:275
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:365
 msgid "Compiling the plugin"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:277
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:367
 msgid ""
 "We cannot easily write by hand a ``SConstruct`` file that SCons would use "
 "for building. For the purpose of this example, just use :download:`this "
@@ -52082,42 +52078,49 @@ msgid ""
 "files in a subsequent tutorial."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:283
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:373
+msgid ""
+"This ``SConstruct`` file was written to be used with the latest godot-cpp "
+"master, you may need to make small changes using it with older versions or "
+"refer to the ``SConstruct`` file in the Godot 3.0 documentation."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:375
 msgid ""
 "Once you've downloaded the ``SConstruct`` file, place it in your GDNative "
 "module folder besides ``godot-cpp``, ``godot_headers`` and ``demo``, then "
 "run:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:291
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:383
 msgid "You should now be able to find the module in ``demo/bin/<platform>``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:295
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
 msgid ""
 "Here, we've compiled both godot-cpp and our gdexample library as debug "
 "builds. For optimized builds, you should compile them using the "
 "``target=release`` switch."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:300
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
 msgid "Using the GDNative module"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:302
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
 msgid ""
 "Before we jump back into Godot, we need to create two more files in ``demo/"
 "bin/``. Both can be created using the Godot editor, but it may be faster to "
 "create them directly."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:306
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
 msgid ""
 "The first one is a file that lets Godot know what dynamic libraries should "
 "be loaded for each platform and is called ``gdexample.gdnlib``."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:329
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:422
 msgid ""
 "This file contains a ``general`` section that controls how the module is "
 "loaded. It also contains a prefix section which should be left on ``godot_`` "
@@ -52127,7 +52130,7 @@ msgid ""
 "linked statically."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:336
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:429
 msgid ""
 "The ``entry`` section is the important bit: it tells Godot the location of "
 "the dynamic library in the project's filesystem for each supported platform. "
@@ -52136,7 +52139,7 @@ msgid ""
 "incompatible with the target platform."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:342
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:435
 msgid ""
 "Finally, the ``dependencies`` section allows you to name additional dynamic "
 "libraries that should be included as well. This is important when your "
@@ -52144,58 +52147,255 @@ msgid ""
 "a third-party dynamic library with your project."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:347
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:440
 msgid ""
 "If you double click on the ``gdexample.gdnlib`` file within Godot, you'll "
 "see there are far more options to set:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:352
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:445
 msgid ""
 "The second file we need to create is a file used by each NativeScript we've "
 "added to our plugin. We'll name it ``gdexample.gdns`` for our gdexample "
 "NativeScript."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:369
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:462
 msgid ""
-"This is a standard Godot resource; you could just create it directly in of "
-"your scene, but saving it to a file makes it much easier to reuse it in "
-"other places. This resource points to our gdnlib file, so that Godot can "
-"know which dynamic library contains our NativeScript. It also defines the "
+"This is a standard Godot resource; you could just create it directly in your "
+"scene, but saving it to a file makes it much easier to reuse it in other "
+"places. This resource points to our gdnlib file, so that Godot can know "
+"which dynamic library contains our NativeScript. It also defines the "
 "``class_name`` which identifies the NativeScript in our plugin we want to "
 "use."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:376
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:469
 msgid ""
 "Time to jump back into Godot. We load up the main scene we created way back "
 "in the beginning and now add a Sprite to our scene:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:381
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:474
 msgid ""
 "We're going to assign the Godot logo to this sprite as our texture, disable "
 "the ``centered`` property and drag our ``gdexample.gdns`` file onto the "
 "``script`` property of the sprite:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:387
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:480
 msgid "We're finally ready to run the project:"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:392
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:485
+msgid "Adding properties"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:487
+msgid ""
+"GDScript allows you to add properties to your script using the ``export`` "
+"keyword. In GDNative you have to register the properties and there are two "
+"ways of doing this. You can either bind directly to a member or use a setter "
+"and getter function."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:493
+msgid ""
+"There is a third option, just like in GDScript you can directly implement "
+"the ``_get_property_list``, ``_get`` and ``_set`` methods of an object but "
+"that goes far beyond the scope of this tutorial."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:497
+msgid ""
+"We'll examine both starting with the direct bind. Lets add a property that "
+"allows us to control the amplitude of our wave."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:500
+msgid ""
+"In our ``gdexample.h`` file we simply need to add a member variable like so:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:510
+msgid ""
+"In our ``gdexample.cpp`` file we need to make a number of changes, we will "
+"only show the methods we end up changing, don't remove the lines we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:562
+msgid ""
+"Once you compile the module with these changes in place you will see that a "
+"property has been added to our interface. You can now change this property "
+"and when you run your project, you will see that our Godot icon travels "
+"along a larger figure."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:567
+msgid ""
+"Lets do the same but for the speed of our animation and use a setter and "
+"getter function. Our ``gdexample.h`` header file again only needs a few more "
+"lines of code:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:581
+msgid ""
+"This requires a few more changes to our ``gdexample.cpp`` file, again we're "
+"only showing the methods that have changed so don't remove anything we're "
+"omitting:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:653
+msgid ""
+"Now when the project is compiled we'll see another property called speed. "
+"Changing its value will make the animation go faster or slower."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:656
+msgid ""
+"For this example there is no obvious advantage of using a setter and getter. "
+"It is just more code to write. For a simple example as this there may be a "
+"good reason for a setter if you want to react on the variable being changed "
+"but in many cases just binding the variable will be enough."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:661
+msgid ""
+"Getters and setters become far more useful in more complex scenarios where "
+"you need to make additional choices based on the state of your object."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:667
+msgid ""
+"For simplicity we've left out the optional parameters in the "
+"register_property<class, type> method call. These parameters are "
+"``rpc_mode``, ``usage``, ``hint`` and ``hint_string``. These can be used to "
+"further configure how properties are displayed and set on the Godot side."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:673
+msgid ""
+"Modern C++ compilers are able to infer the class and variable type and allow "
+"you to omit the ``<GDExample, float>`` part of our ``register_property`` "
+"method. we've had mixed experiences with this however."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:681
+msgid ""
+"Last but not least, signals fully work in GDNative as well. Having your "
+"module react to a signal given out by another object requires you to call "
+"``connect`` on that object. We can't think of a good example for our "
+"wobbling Godot icon, we would need to showcase a far more complete example."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:687
+msgid "This however is the required syntax:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:698
+msgid ""
+"Note that you can only call ``my_method`` if you've previously registered it "
+"in your ``_register_methods`` method."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:701
+msgid ""
+"Having your object sending out signals is far more common. For our wobbling "
+"Godot icon we'll do something silly just to show how it works. We're going "
+"to emit a signal every time a second has passed and pass the new location "
+"along."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:706
+msgid ""
+"In our ``gdexample.h`` header file we just need to define a new member "
+"``time_emit``:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:716
+msgid ""
+"The changes in ``gdexample.cpp`` are a bit more elaborate this time. First "
+"you'll need to set ``time_emit = 0.0;`` in either our ``_init`` method or in "
+"our constructor. But the other two needed changes we'll look at one by one."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:720
+msgid ""
+"In our ``_register_methods`` method we need to declare our signal and we do "
+"this as follows:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:747
+msgid ""
+"Here we see a nice improvement in the latest version of godot-cpp where our "
+"``register_signal`` method can be a single call first taking the signals "
+"name, then having pairs of values specificying the parameter name and type "
+"of each parameter we'll send along with this signal."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:752
+msgid ""
+"For NativeScript 1.0 we first build a dictionary in which we tell Godot "
+"about the types of arguments we will pass to our signal, and then register "
+"it."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:755
+msgid "Next we'll need to change our ``_process`` method:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:801
+msgid ""
+"After a second has passed we emit our signal and reset our counter. Again in "
+"the new version of godot-cpp we can add our parameter values directly to "
+"``emit_signal``. In NativeScript 1.0 We first build an array of values and "
+"then call ``emit_signal``."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:807
+msgid ""
+"Once compiled we can go into Godot and select our sprite node. On our "
+"``Node`` tab we find our new signal and link it up by pressing connect. "
+"We've added a script on our main node and implemented our signal like this:"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:818
+msgid "Every second we simply output our position to the console."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:822
+msgid "NativeScript 1.1 v.s. NativeScript 1.0"
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:824
+msgid ""
+"So far in our example above there doesn't seem to be a lot of difference "
+"between the old and new syntax. The class is defined slightly differently "
+"and we no longer use the ``owner`` member to call methods on the Godot side "
+"of our object. A lot of the improvements are hidden under the hood."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:829
+msgid ""
+"This example only deals with simple variables and simple methods. Especially "
+"once you start passing references to other objects or when you start calling "
+"methods that require more complex parameters, NativeScript 1.1 does start to "
+"show its benefits."
+msgstr ""
+
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:835
 msgid "Next steps"
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:394
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:837
 msgid ""
 "The above is only a simple example, but we hope it shows you the basics. You "
 "can build upon this example to create full-fledged scripts to control nodes "
 "in Godot using C++."
 msgstr ""
 
-#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:398
+#: ../../docs/tutorials/plugins/gdnative/gdnative-cpp-example.rst:841
 msgid ""
 "You should be able to edit and recompile the plugin while the Godot editor "
 "remains open; just rerun the project after the library has finished building."
@@ -54286,7 +54486,7 @@ msgid ""
 "it if you are planning to build Godot yourself."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:42
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:43
 msgid ""
 "Please refer to the documentation for :ref:`doc_compiling_for_android`, :ref:"
 "`doc_compiling_for_ios`, :ref:`doc_compiling_for_osx`, :ref:"
@@ -54294,18 +54494,18 @@ msgid ""
 "`doc_compiling_for_windows` and :ref:`doc_compiling_for_x11`."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:44
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:45
 msgid ""
 "Note that for **Windows/Visual Studio**, you need to use ``x86_x64 Cross "
 "Tools Command Prompt for VS 2017`` or similar, depending on your install, "
 "instead of the standard Windows command prompt to enter the commands below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:47
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:48
 msgid "Platform selection"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:49
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:50
 msgid ""
 "Godot's build system will begin by detecting the platforms it can build for. "
 "If not detected, the platform will simply not appear on the list of "
@@ -54313,23 +54513,23 @@ msgid ""
 "in the rest of this tutorial section."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:54
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:55
 msgid "SCons is invoked by just calling ``scons``."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:56
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:57
 msgid ""
 "However, this will do nothing except list the available platforms, for "
 "example:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:77
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:78
 msgid ""
 "To build for a platform (for example, x11), run with the ``platform=`` (or "
 "just ``p=`` to make it short) argument:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:84
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:85
 msgid ""
 "This will start the build process, which will take a while. If you want "
 "scons to build faster, use the ``-j <cores>`` parameter to specify how many "
@@ -54337,35 +54537,35 @@ msgid ""
 "can use your computer for something else :)"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:89
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:90
 msgid "Example for using 4 cores:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:96
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:97
 msgid "Resulting binary"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:98
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:99
 msgid ""
 "The resulting binaries will be placed in the bin/ subdirectory, generally "
 "with this naming convention:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:105
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:106
 msgid "For the previous build attempt the result would look like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:112
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:113
 msgid ""
 "This means that the binary is for X11, is not optimized, has tools (the "
 "whole editor) compiled in, and is meant for 64 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:115
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:116
 msgid "A Windows binary with the same configuration will look like this."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:122
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:123
 msgid ""
 "Just copy that binary to wherever you like, as it contains the project "
 "manager, editor and all means to execute the game. However, it lacks the "
@@ -54374,103 +54574,103 @@ msgid ""
 "godotengine.org/>`__, or you can build them yourself)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:128
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:129
 msgid ""
 "Aside from that, there are a few standard options that can be set in all "
 "build targets, and which will be explained below."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:134
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:135
 msgid ""
 "Tools are enabled by default in all PC targets (Linux, Windows, macOS), "
 "disabled for everything else. Disabling tools produces a binary that can run "
 "projects but that does not include the editor or the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:144
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:145
 msgid "Target"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:146
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:147
 msgid "Target controls optimization and debug flags. Each mode means:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:148
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:149
 msgid ""
 "**debug**: Build with C++ debugging symbols, runtime checks (performs checks "
 "and reports error) and none to little optimization."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:150
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:151
 msgid ""
 "**release_debug**: Build without C++ debugging symbols and optimization, but "
 "keep the runtime checks (performs checks and reports errors). Official "
 "binaries use this configuration."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:153
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:154
 msgid ""
 "**release**: Build without symbols, with optimization and with little to no "
 "runtime checks. This target can't be used together with tools=yes, as the "
 "tools require some debug functionality and run-time checks to run."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:162
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:163
 msgid ""
 "This flag appends the \".debug\" suffix (for debug), or \".tools\" (for "
 "debug with tools enabled). When optimization is enabled (release) it appends "
 "the \".opt\" suffix."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:167
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:168
 msgid "Bits"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:169
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:170
 msgid ""
 "Bits is meant to control the CPU or OS version intended to run the binaries. "
 "It is focused mostly on desktop platforms and ignored everywhere else."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:173
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
 msgid "**32**: Build binaries for 32 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:174
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
 msgid "**64**: Build binaries for 64 bits platform."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:175
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:176
 msgid ""
 "**default**: Build whatever the build system feels is best. On Linux this "
 "depends on the host platform (if not cross compiling), on Mac it defaults to "
 "64 bits and on Windows it defaults to 32 bits."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:183
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:184
 msgid ""
 "This flag appends \".32\" or \".64\" suffixes to resulting binaries when "
 "relevant."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:187
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:188
 msgid "Other build options"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:189
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:190
 msgid ""
 "There are several other build options that you can use to configure the way "
 "Godot should be built (compiler, debug options, etc.) as well as the "
 "features to include/disable."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:193
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:194
 msgid ""
 "Check the output of ``scons --help`` for details about each option for the "
 "version you are willing to compile."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:199
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:200
 msgid ""
 "Official export templates are downloaded from the Godot Engine site: "
 "`godotengine.org <https://godotengine.org/>`__. However, you might want to "
@@ -54478,20 +54678,20 @@ msgid ""
 "modules, or simply don't trust your own shadow)."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:204
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:205
 msgid ""
 "If you download the official export templates package and unzip it, you will "
 "notice that most are just optimized binaries or packages for each platform:"
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:227
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:228
 msgid ""
 "To create those yourself, just follow the instructions detailed for each "
 "platform in this same tutorial section. Each platform explains how to create "
 "its own template."
 msgstr ""
 
-#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:231
+#: ../../docs/development/compiling/introduction_to_the_buildsystem.rst:232
 msgid ""
 "If you are developing for multiple platforms, macOS is definitely the most "
 "convenient host platform for cross compilation, since you can cross-compile "
@@ -54530,11 +54730,23 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:24
+#: ../../docs/development/compiling/compiling_for_windows.rst:23
+#: ../../docs/development/compiling/compiling_for_x11.rst:27
+#: ../../docs/development/compiling/compiling_for_osx.rst:18
+#: ../../docs/development/compiling/compiling_for_android.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:15
+#: ../../docs/development/compiling/compiling_for_uwp.rst:20
+#: ../../docs/development/compiling/compiling_for_web.rst:19
+msgid ""
+"For a general overview of SCons usage for Godot, see :ref:"
+"`doc_introduction_to_the_buildsystem`."
+msgstr ""
+
+#: ../../docs/development/compiling/compiling_for_windows.rst:27
 msgid "Setting up SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:26
+#: ../../docs/development/compiling/compiling_for_windows.rst:29
 msgid ""
 "Python adds the interpreter (python.exe) to the path. It usually installs in "
 "``C:\\Python`` (or ``C:\\Python[Version]``). SCons installs inside the "
@@ -54544,24 +54756,24 @@ msgid ""
 "interpreter executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:33
+#: ../../docs/development/compiling/compiling_for_windows.rst:36
 msgid ""
 "To check whether you have installed Python and SCons correctly, you can type "
 "``python --version`` and ``scons --version`` into the Windows Command Prompt "
 "(``cmd.exe``)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:37
+#: ../../docs/development/compiling/compiling_for_windows.rst:40
 msgid ""
 "If commands above do not work, make sure you add Python to your PATH "
 "environment variable after installing it, and check again."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:41
+#: ../../docs/development/compiling/compiling_for_windows.rst:44
 msgid "Setting up Pywin32"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:43
+#: ../../docs/development/compiling/compiling_for_windows.rst:46
 msgid ""
 "Pywin32 is required for parallel builds using multiple CPU cores. If SCons "
 "is issuing a warning about Pywin32 after parsing SConstruct build "
@@ -54570,7 +54782,7 @@ msgid ""
 "<https://github.com/mhammond/pywin32/releases>`__"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:49
+#: ../../docs/development/compiling/compiling_for_windows.rst:52
 msgid ""
 "For example, if you installed a 32-bit version of Python 2.7, you would want "
 "to install the latest version of Pywin32 that is built for the mentioned "
@@ -54578,18 +54790,18 @@ msgid ""
 "win32-py2.7.exe``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:53
+#: ../../docs/development/compiling/compiling_for_windows.rst:56
 msgid ""
 "The ``amd64`` version of Pywin32 is for a 64-bit version of Python "
 "``pywin32-221.win-amd64-py2.7.exe``. Change the ``py`` number to install for "
 "your version of Python (check via ``python --version`` mentioned above)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:60
+#: ../../docs/development/compiling/compiling_for_windows.rst:63
 msgid "Installing Visual Studio caveats"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:62
+#: ../../docs/development/compiling/compiling_for_windows.rst:65
 msgid ""
 "If installing Visual Studio 2015 or later, make sure to run **Custom** "
 "installation, not **Typical** and select C++ as language there (and any "
@@ -54599,7 +54811,7 @@ msgid ""
 ">`__ in Visual Studio 2015."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:68
+#: ../../docs/development/compiling/compiling_for_windows.rst:71
 msgid ""
 "If you have already made the mistake of installing a **Typical**, "
 "installation, rerun the executable installer you downloaded from internet, "
@@ -54608,37 +54820,37 @@ msgid ""
 "nothing for your problem."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:74
+#: ../../docs/development/compiling/compiling_for_windows.rst:77
 msgid ""
 "If you're using Express, make sure you get/have a version that can compile "
 "for ***C++, Desktop***."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:78
+#: ../../docs/development/compiling/compiling_for_windows.rst:81
 msgid "Downloading Godot's source"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:80
+#: ../../docs/development/compiling/compiling_for_windows.rst:83
 msgid ""
 "`Godot's <https://github.com/godotengine/godot>`__ source is hosted on "
 "GitHub. Downloading it (cloning) via `Git <https://git-scm.com/>`__ is "
 "recommended."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:83
+#: ../../docs/development/compiling/compiling_for_windows.rst:86
 msgid ""
 "The tutorial will presume from now on that you placed the source into ``C:"
 "\\godot``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:89
+#: ../../docs/development/compiling/compiling_for_windows.rst:92
 msgid ""
 "SCons will not be able out of the box to compile from the Windows Command "
 "Prompt (``cmd.exe``) because SCons and Visual C++ compiler will not be able "
 "to locate environment variables and executables they need for compilation."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:94
+#: ../../docs/development/compiling/compiling_for_windows.rst:97
 msgid ""
 "Therefore, you need to start a Visual Studio command prompt. It sets up "
 "environment variables needed by SCons to locate the compiler. It should be "
@@ -54646,63 +54858,63 @@ msgid ""
 "Visual Studio):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:99
+#: ../../docs/development/compiling/compiling_for_windows.rst:102
 msgid "\"Developer Command Prompt for VS2013\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:100
+#: ../../docs/development/compiling/compiling_for_windows.rst:103
 msgid "\"VS2013 x64 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:101
+#: ../../docs/development/compiling/compiling_for_windows.rst:104
 msgid "\"VS2013 x86 Native Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:102
+#: ../../docs/development/compiling/compiling_for_windows.rst:105
 msgid "\"VS2013 x64 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:103
+#: ../../docs/development/compiling/compiling_for_windows.rst:106
 msgid "\"VS2013 x86 Cross Tools Command Prompt\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:105
+#: ../../docs/development/compiling/compiling_for_windows.rst:108
 msgid ""
 "You should be able to find at least the Developer Command Prompt for your "
 "version of Visual Studio in your start menu."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:111
 msgid ""
 "However Visual Studio sometimes seems to not install some of the above "
 "shortcuts, except the Developer Console at these locations that are "
 "automatically searched by the start menu search option:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:118
+#: ../../docs/development/compiling/compiling_for_windows.rst:121
 msgid ""
 "If you found the Developer Console, it will do for now to create a 32-bit "
 "version of Godot, but if you want the 64-bit version, you might need to "
 "setup the prompts manually for easy access."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:122
+#: ../../docs/development/compiling/compiling_for_windows.rst:125
 msgid ""
 "If you don't see some of the shortcuts, \"How the prompts actually work\" "
 "section below will explain how to setup these prompts if you need them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:126
+#: ../../docs/development/compiling/compiling_for_windows.rst:129
 msgid "About the Developer/Tools Command Prompts and the Visual C++ compiler"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:128
+#: ../../docs/development/compiling/compiling_for_windows.rst:131
 msgid ""
 "There is a few things you need to know about these consoles and the Visual C+"
 "+ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:131
+#: ../../docs/development/compiling/compiling_for_windows.rst:134
 msgid ""
 "Your Visual Studio installation will ship with several Visual C++ compilers, "
 "them being more or less identical, however each ``cl.exe`` (Visual C++ "
@@ -54710,13 +54922,13 @@ msgid ""
 "bit x86; the ARM compiler is not supported)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:136
+#: ../../docs/development/compiling/compiling_for_windows.rst:139
 msgid ""
 "The **Developer Command Prompt** will build a 32-bit version of Godot by "
 "using the 32-bit Visual C++ compiler."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:139
+#: ../../docs/development/compiling/compiling_for_windows.rst:142
 msgid ""
 "**Native Tools** Prompts (mentioned above) are used when you want the 32-bit "
 "cl.exe to compile a 32-bit executable (x86 Native Tools Command Prompt). For "
@@ -54724,7 +54936,7 @@ msgid ""
 "Command Prompt)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:144
+#: ../../docs/development/compiling/compiling_for_windows.rst:147
 msgid ""
 "The **Cross Tools** are used when your Windows is using one architecture (32-"
 "bit, for example) and you need to compile to a different architecture (64-"
@@ -54732,25 +54944,25 @@ msgid ""
 "executables, but you still might need to compile for them."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:149
+#: ../../docs/development/compiling/compiling_for_windows.rst:152
 #: ../../docs/development/cpp/object_class.rst:134
 msgid "For example:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:151
+#: ../../docs/development/compiling/compiling_for_windows.rst:154
 msgid ""
 "\"VS2013 x64 Cross Tools Command Prompt\" will use a 32-bit cl.exe that will "
 "compile a 64 bit application."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:154
+#: ../../docs/development/compiling/compiling_for_windows.rst:157
 msgid ""
 "\"VS2013 x86 Cross Tools Command Prompt\" will use a 64-bit cl.exe that will "
 "compile a 32-bit application. This one is useful if you are running a 32-bit "
 "Windows."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:158
+#: ../../docs/development/compiling/compiling_for_windows.rst:161
 msgid ""
 "On a 64-bit Windows, you can run any of above prompts and compilers (``cl."
 "exe`` executables) because 64-bit Windows can run any 32-bit application. 32-"
@@ -54758,30 +54970,30 @@ msgid ""
 "won't even install shortcuts for some of these prompts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:164
+#: ../../docs/development/compiling/compiling_for_windows.rst:167
 msgid ""
 "Note that you need to choose the **Developer Console** or the correct "
 "**Tools Prompt** to build Godot for the correct architecture. Use only "
 "Native Prompts if you are not sure yet what exactly Cross Compile Prompts do."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:170
+#: ../../docs/development/compiling/compiling_for_windows.rst:173
 msgid "Running SCons"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:172
+#: ../../docs/development/compiling/compiling_for_windows.rst:175
 msgid ""
 "Once inside the **Developer Console/Tools Console Prompt**, go to the root "
 "directory of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:179
+#: ../../docs/development/compiling/compiling_for_windows.rst:182
 msgid ""
 "Tip: if you installed \"Pywin32 Python Extension\" you can append the -j "
 "command to instruct SCons to run parallel builds like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:186
+#: ../../docs/development/compiling/compiling_for_windows.rst:189
 msgid ""
 "In general, it is OK to have at least as many threads compiling Godot as you "
 "have cores in your CPU, if not one or two more. Feel free to add the -j "
@@ -54789,7 +55001,7 @@ msgid ""
 "Extension\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:191
+#: ../../docs/development/compiling/compiling_for_windows.rst:194
 msgid ""
 "If all goes well, the resulting binary executable will be placed in ``C:"
 "\\godot\\bin\\`` with the name of ``godot.windows.tools.32.exe`` or ``godot."
@@ -54798,25 +55010,25 @@ msgid ""
 "corresponding executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:197
+#: ../../docs/development/compiling/compiling_for_windows.rst:200
 msgid ""
 "This executable file contains the whole engine and runs without any "
 "dependencies. Executing it will bring up the Project Manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:200
-#: ../../docs/development/compiling/compiling_for_x11.rst:108
+#: ../../docs/development/compiling/compiling_for_windows.rst:203
+#: ../../docs/development/compiling/compiling_for_x11.rst:111
 msgid ""
 "If you are compiling Godot for production use, then you can make the final "
 "executable smaller and faster by adding the SCons option "
 "``target=release_debug``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:205
+#: ../../docs/development/compiling/compiling_for_windows.rst:208
 msgid "How the prompts actually work"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:207
+#: ../../docs/development/compiling/compiling_for_windows.rst:210
 msgid ""
 "The Visual Studio command prompts are just shortcuts that call the standard "
 "Command Prompt and have it run a batch file before giving  you control. The "
@@ -54827,46 +55039,46 @@ msgid ""
 "enables are needed by Godot/SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:215
+#: ../../docs/development/compiling/compiling_for_windows.rst:218
 msgid ""
 "Since you are probably using Visual Studio 2013 or 2015, if you need to "
 "recreate them manually, use the below folders, or place them on the desktop/"
 "taskbar:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:224
+#: ../../docs/development/compiling/compiling_for_windows.rst:227
 msgid ""
 "Start the creation of the shortcut by pressing the ``right mouse button/New/"
 "Shortcut`` in an empty place in your desired location."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:227
+#: ../../docs/development/compiling/compiling_for_windows.rst:230
 msgid ""
 "Then copy one of these commands below for the corresponding tool you need "
 "into the \"Path\" and \"Name\" sections of the shortcut creation wizard, and "
 "fix the path to the batch file if needed."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:231
+#: ../../docs/development/compiling/compiling_for_windows.rst:234
 msgid "Visual Studio 2013 is in the \"Microsoft Visual Studio 12.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:232
+#: ../../docs/development/compiling/compiling_for_windows.rst:235
 msgid "Visual Studio 2015 is in the \"Microsoft Visual Studio 14.0\" folder."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:233
+#: ../../docs/development/compiling/compiling_for_windows.rst:236
 msgid "etc."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:252
+#: ../../docs/development/compiling/compiling_for_windows.rst:255
 msgid ""
 "After you create the shortcut, in the shortcut's properties, that you can "
 "access by right clicking with your mouse on the shortcut itself, you can "
 "choose the starting directory of the command prompt (\"Start in\" field)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:257
+#: ../../docs/development/compiling/compiling_for_windows.rst:260
 msgid ""
 "Some of these shortcuts (namely the 64-bit compilers) seem to not be "
 "available in the Express edition of Visual Studio or Visual C++. Before "
@@ -54875,68 +55087,68 @@ msgid ""
 "architecture you want to build from the command prompt."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:278
+#: ../../docs/development/compiling/compiling_for_windows.rst:281
 msgid ""
 "In case you are wondering what these prompt shortcuts do, they call ``cmd."
 "exe`` with the ``\\k`` option and have it run a Batch file."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:290
+#: ../../docs/development/compiling/compiling_for_windows.rst:293
 msgid "How to run an automated build of Godot"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:292
+#: ../../docs/development/compiling/compiling_for_windows.rst:295
 msgid ""
 "If you just need to run the compilation process via a Batch file or directly "
 "in the Windows Command Prompt you need to use the following command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:300
+#: ../../docs/development/compiling/compiling_for_windows.rst:303
 msgid "with one of the following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:302
+#: ../../docs/development/compiling/compiling_for_windows.rst:305
 msgid "x86 (32-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:303
+#: ../../docs/development/compiling/compiling_for_windows.rst:306
 msgid "amd64 (64-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:304
+#: ../../docs/development/compiling/compiling_for_windows.rst:307
 msgid "x86_amd64 (32-bit cl.exe to compile for the 64-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:305
+#: ../../docs/development/compiling/compiling_for_windows.rst:308
 msgid "amd64_x86 (64-bit cl.exe to compile for the 32-bit architecture)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:307
+#: ../../docs/development/compiling/compiling_for_windows.rst:310
 msgid "and after that one, you can run SCons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:313
+#: ../../docs/development/compiling/compiling_for_windows.rst:316
 msgid "or you can run them together:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:324
+#: ../../docs/development/compiling/compiling_for_windows.rst:327
 msgid "Development in Visual Studio or other IDEs"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:326
+#: ../../docs/development/compiling/compiling_for_windows.rst:329
 msgid ""
 "For most projects, using only scripting is enough but when development in C+"
 "+ is needed, for creating modules or extending the engine, working with an "
 "IDE is usually desirable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:330
+#: ../../docs/development/compiling/compiling_for_windows.rst:333
 msgid ""
 "You can create a Visual Studio solution via SCons by running SCons with the "
 "``vsproj=yes`` parameter, like this:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:337
+#: ../../docs/development/compiling/compiling_for_windows.rst:340
 msgid ""
 "You will be able to open Godot's source in a Visual Studio solution now, and "
 "able to build Godot via the Visual Studio **Build** button. However, make "
@@ -54944,7 +55156,7 @@ msgid ""
 "properly."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:342
+#: ../../docs/development/compiling/compiling_for_windows.rst:345
 msgid ""
 "If you need to edit the compilation commands, they are located in \"Godot\" "
 "project settings, NMAKE sheet. SCons is called at the end of the commands. "
@@ -54953,11 +55165,11 @@ msgid ""
 "They are equivalent."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:349
+#: ../../docs/development/compiling/compiling_for_windows.rst:352
 msgid "Cross-compiling for Windows from other operating systems"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:351
+#: ../../docs/development/compiling/compiling_for_windows.rst:354
 msgid ""
 "If you are a Linux or macOS user, you need to install `MinGW-w64 <https://"
 "mingw-w64.org/doku.php>`_, which typically comes in 32-bit and 64-bit "
@@ -54965,114 +55177,114 @@ msgid ""
 "known ones:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:356
-#: ../../docs/development/compiling/compiling_for_x11.rst:30
+#: ../../docs/development/compiling/compiling_for_windows.rst:359
+#: ../../docs/development/compiling/compiling_for_x11.rst:33
 msgid "**Arch**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:360
-#: ../../docs/development/compiling/compiling_for_x11.rst:34
+#: ../../docs/development/compiling/compiling_for_windows.rst:363
+#: ../../docs/development/compiling/compiling_for_x11.rst:37
 msgid "**Debian** / **Ubuntu**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:364
-#: ../../docs/development/compiling/compiling_for_x11.rst:40
+#: ../../docs/development/compiling/compiling_for_windows.rst:367
+#: ../../docs/development/compiling/compiling_for_x11.rst:43
 msgid "**Fedora**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:368
+#: ../../docs/development/compiling/compiling_for_windows.rst:371
 msgid "**macOS**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:372
-#: ../../docs/development/compiling/compiling_for_x11.rst:57
+#: ../../docs/development/compiling/compiling_for_windows.rst:375
+#: ../../docs/development/compiling/compiling_for_x11.rst:60
 msgid "**Mageia**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:377
+#: ../../docs/development/compiling/compiling_for_windows.rst:380
 msgid ""
 "Before allowing you to attempt the compilation, SCons will check for the "
 "following binaries in your ``$PATH``:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:385
+#: ../../docs/development/compiling/compiling_for_windows.rst:388
 msgid ""
 "If the binaries are not located in the ``$PATH`` (e.g. ``/usr/bin``), you "
 "can define the following environment variables to give a hint to the build "
 "system:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:394
+#: ../../docs/development/compiling/compiling_for_windows.rst:397
 msgid ""
 "To make sure you are doing things correctly, executing the following in the "
 "shell should result in a working compiler (the version output may differ "
 "based on your system):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:404
-#: ../../docs/development/compiling/compiling_for_android.rst:131
-#: ../../docs/development/compiling/compiling_for_android.rst:178
+#: ../../docs/development/compiling/compiling_for_windows.rst:407
+#: ../../docs/development/compiling/compiling_for_android.rst:122
+#: ../../docs/development/compiling/compiling_for_android.rst:169
 #: ../../docs/development/cpp/creating_android_modules.rst:335
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:406
+#: ../../docs/development/compiling/compiling_for_windows.rst:409
 msgid ""
 "Cross-compiling from some versions of Ubuntu may lead to `this bug <https://"
 "github.com/godotengine/godot/issues/9258>`_, due to a default configuration "
 "lacking support for POSIX threading."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:409
+#: ../../docs/development/compiling/compiling_for_windows.rst:412
 msgid ""
 "You can change that configuration following those instructions, for 32-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:419
+#: ../../docs/development/compiling/compiling_for_windows.rst:422
 msgid "And for 64-bit:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:429
+#: ../../docs/development/compiling/compiling_for_windows.rst:432
 msgid "Creating Windows export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:431
+#: ../../docs/development/compiling/compiling_for_windows.rst:434
 msgid ""
 "Windows export templates are created by compiling Godot as release, with the "
 "following flags:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:434
+#: ../../docs/development/compiling/compiling_for_windows.rst:437
 msgid "(using Mingw32 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:441
+#: ../../docs/development/compiling/compiling_for_windows.rst:444
 msgid "(using Mingw-w64 command prompt, using the bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:448
+#: ../../docs/development/compiling/compiling_for_windows.rst:451
 msgid ""
 "(using the Visual Studio command prompts for the correct architecture, "
 "notice the lack of bits parameter)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:456
+#: ../../docs/development/compiling/compiling_for_windows.rst:459
 msgid "If you plan on replacing the standard templates, copy these to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:462
+#: ../../docs/development/compiling/compiling_for_windows.rst:465
 msgid "With the following names:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:471
-#: ../../docs/development/compiling/compiling_for_x11.rst:150
+#: ../../docs/development/compiling/compiling_for_windows.rst:474
+#: ../../docs/development/compiling/compiling_for_x11.rst:153
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your binaries as custom export templates "
 "here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_windows.rst:477
+#: ../../docs/development/compiling/compiling_for_windows.rst:480
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the ``bin\\`` directory of your Godot source folder, so the next time you "
@@ -55139,37 +55351,37 @@ msgstr ""
 msgid "*Optional* - yasm (for WebM SIMD optimizations)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:28
+#: ../../docs/development/compiling/compiling_for_x11.rst:31
 msgid "Distro-specific oneliners"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:46
+#: ../../docs/development/compiling/compiling_for_x11.rst:49
 msgid "**FreeBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:51
+#: ../../docs/development/compiling/compiling_for_x11.rst:54
 msgid "**Gentoo**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:63
+#: ../../docs/development/compiling/compiling_for_x11.rst:66
 msgid "**OpenBSD**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:67
+#: ../../docs/development/compiling/compiling_for_x11.rst:70
 msgid "**openSUSE**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:73
+#: ../../docs/development/compiling/compiling_for_x11.rst:76
 msgid "**Solus**"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:82
-#: ../../docs/development/compiling/compiling_for_osx.rst:21
+#: ../../docs/development/compiling/compiling_for_x11.rst:85
+#: ../../docs/development/compiling/compiling_for_osx.rst:24
 msgid ""
 "Start a terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:88
+#: ../../docs/development/compiling/compiling_for_x11.rst:91
 msgid ""
 "A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as "
 "many threads compiling Godot as you have cores in your CPU, if not one or "
@@ -55177,61 +55389,61 @@ msgid ""
 "below."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:92
-#: ../../docs/development/compiling/compiling_for_osx.rst:27
+#: ../../docs/development/compiling/compiling_for_x11.rst:95
+#: ../../docs/development/compiling/compiling_for_osx.rst:30
 msgid ""
 "If all goes well, the resulting binary executable will be placed in the \"bin"
 "\" subdirectory. This executable file contains the whole engine and runs "
 "without any dependencies. Executing it will bring up the project manager."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:99
+#: ../../docs/development/compiling/compiling_for_x11.rst:102
 msgid "If you wish to compile using Clang rather than GCC, use this command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:105
+#: ../../docs/development/compiling/compiling_for_x11.rst:108
 msgid ""
 "Using Clang appears to be a requirement for OpenBSD, otherwise fonts would "
 "not build."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:113
-#: ../../docs/development/compiling/compiling_for_web.rst:20
+#: ../../docs/development/compiling/compiling_for_x11.rst:116
+#: ../../docs/development/compiling/compiling_for_web.rst:23
 msgid "Building export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:115
+#: ../../docs/development/compiling/compiling_for_x11.rst:118
 msgid ""
 "To build X11 (Linux, \\*BSD) export templates, run the build system with the "
 "following parameters:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:118
+#: ../../docs/development/compiling/compiling_for_x11.rst:121
 msgid "(32 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:125
+#: ../../docs/development/compiling/compiling_for_x11.rst:128
 msgid "(64 bits)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:132
+#: ../../docs/development/compiling/compiling_for_x11.rst:135
 msgid ""
 "Note that cross compiling for the opposite bits (64/32) as your host "
 "platform is not always straight-forward and might need a chroot environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:135
+#: ../../docs/development/compiling/compiling_for_x11.rst:138
 msgid ""
 "To create standard export templates, the resulting files must be copied to:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:141
+#: ../../docs/development/compiling/compiling_for_x11.rst:144
 msgid ""
 "and named like this (even for \\*BSD which is seen as \"Linux X11\" by "
 "Godot):"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_x11.rst:156
+#: ../../docs/development/compiling/compiling_for_x11.rst:159
 msgid ""
 "You don't even need to copy them, you can just reference the resulting files "
 "in the bin/ directory of your Godot source folder, so the next time you "
@@ -55251,18 +55463,18 @@ msgstr ""
 msgid "Xcode (or the more lightweight Command Line Tools for Xcode)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:32
+#: ../../docs/development/compiling/compiling_for_osx.rst:35
 msgid ""
 "To create an .app like in the official builds, you need to use the template "
 "located in ``misc/dist/osx_tools.app``. Typically, for a \".64\" optimised "
 "binary built with `scons p=osx target=release_debug`:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:44
+#: ../../docs/development/compiling/compiling_for_osx.rst:47
 msgid "Compiling for 32 and 64-bit"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:46
+#: ../../docs/development/compiling/compiling_for_osx.rst:49
 msgid ""
 "All macOS versions after 10.6 are 64-bit exclusive, so the executable will "
 "be a \".64\" file by default for most users. If you would like to compile a "
@@ -55270,11 +55482,11 @@ msgid ""
 "specifying the bits in the scons command like so:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:56
+#: ../../docs/development/compiling/compiling_for_osx.rst:59
 msgid "Cross-compiling"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:58
+#: ../../docs/development/compiling/compiling_for_osx.rst:61
 msgid ""
 "It is possible to compile for macOS in a Linux environment (and maybe also "
 "in Windows with Cygwin). For that you will need `OSXCross <https://github."
@@ -55282,37 +55494,37 @@ msgid ""
 "follow the instructions to install it:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:63
+#: ../../docs/development/compiling/compiling_for_osx.rst:66
 msgid ""
 "Clone the `OSXCross repository <https://github.com/tpoechtrager/osxcross>` "
 "somewhere on your machine (or download a zip file and extract it somewhere), "
 "e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:71
+#: ../../docs/development/compiling/compiling_for_osx.rst:74
 msgid ""
 "Follow the instructions to package the SDK: https://github.com/tpoechtrager/"
 "osxcross#packaging-the-sdk"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:73
+#: ../../docs/development/compiling/compiling_for_osx.rst:76
 msgid ""
 "Follow the instructions to install OSXCross: https://github.com/tpoechtrager/"
 "osxcross#installation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:76
+#: ../../docs/development/compiling/compiling_for_osx.rst:79
 msgid ""
 "After that, you will need to define the ``OSXCROSS_ROOT`` as the path to the "
 "OSXCross installation (the same place where you cloned the repository/"
 "extracted the zip), e.g.:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:84
+#: ../../docs/development/compiling/compiling_for_osx.rst:87
 msgid "Now you can compile with SCons like you normally would:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_osx.rst:90
+#: ../../docs/development/compiling/compiling_for_osx.rst:93
 msgid ""
 "If you have an OSXCross SDK version different from the one expected by the "
 "SCons buildsystem, you can specify a custom one with the ``osxcross_sdk`` "
@@ -55373,27 +55585,27 @@ msgid ""
 "current Gradle."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:34
+#: ../../docs/development/compiling/compiling_for_android.rst:37
 msgid "Setting up the buildsystem"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:36
+#: ../../docs/development/compiling/compiling_for_android.rst:39
 msgid "Set the environment variable ANDROID_HOME to point to the Android SDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:39
+#: ../../docs/development/compiling/compiling_for_android.rst:42
 msgid ""
 "Set the environment variable ANDROID_NDK_ROOT to point to the Android NDK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:42
+#: ../../docs/development/compiling/compiling_for_android.rst:45
 msgid ""
 "To set those environment variables on Windows, press Windows+R, type "
 "\"control system\", then click on **Advanced system settings** in the left "
 "pane, then click on **Environment variables** on the window that appears."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:47
+#: ../../docs/development/compiling/compiling_for_android.rst:50
 msgid ""
 "To set those environment variables on Unix (e.g. Linux, macOS), use ``export "
 "ANDROID_HOME=/path/to/android-sdk`` and ``export ANDROID_NDK_ROOT=/path/to/"
@@ -55401,24 +55613,11 @@ msgid ""
 "path where Android SDK and Android NDK are placed on your PC."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:54
-#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
-msgid "Toolchain"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:56
-msgid ""
-"We usually try to keep the Godot Android build code up to date, but Google "
-"changes their toolchain versions often, so if compilation fails due to wrong "
-"toolchain version, go to your NDK directory and check the current number, "
-"then set the following environment variable:"
-msgstr ""
-
-#: ../../docs/development/compiling/compiling_for_android.rst:66
+#: ../../docs/development/compiling/compiling_for_android.rst:57
 msgid "Building the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:68
+#: ../../docs/development/compiling/compiling_for_android.rst:59
 msgid ""
 "Godot needs two export templates for Android: the optimized \"release\" "
 "template (`android_release.apk`) and the debug version (`android_debug."
@@ -55426,29 +55625,29 @@ msgid ""
 "the following arguments:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:73
+#: ../../docs/development/compiling/compiling_for_android.rst:64
 msgid "Release template (used when exporting with \"Debugging Enabled\" OFF)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:81
+#: ../../docs/development/compiling/compiling_for_android.rst:72
 msgid ""
 "(on Linux or macOS, execute the `gradlew` script with `./gradlew build`)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:83
-#: ../../docs/development/compiling/compiling_for_android.rst:97
+#: ../../docs/development/compiling/compiling_for_android.rst:74
+#: ../../docs/development/compiling/compiling_for_android.rst:88
 msgid "The resulting APK is in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:89
+#: ../../docs/development/compiling/compiling_for_android.rst:80
 msgid "Debug template (used when exporting with \"Debugging Enabled\" ON)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:104
+#: ../../docs/development/compiling/compiling_for_android.rst:95
 msgid "Faster compilation"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:106
+#: ../../docs/development/compiling/compiling_for_android.rst:97
 msgid ""
 "If you are on Unix or installed PyWin32 on Windows and have multiple CPU "
 "cores available, you can speed up the compilation by adding the ``-jX`` "
@@ -55456,35 +55655,35 @@ msgid ""
 "want to allocate to the compilation, e.g. ``scons -j4``."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:113
+#: ../../docs/development/compiling/compiling_for_android.rst:104
 msgid "Adding support for x86 devices"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:115
+#: ../../docs/development/compiling/compiling_for_android.rst:106
 msgid ""
 "If you also want to include support for x86 devices, run the scons command a "
 "second time with the ``android_arch=x86`` argument before building the APK "
 "with Gradle. For example for the release template:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:127
+#: ../../docs/development/compiling/compiling_for_android.rst:118
 msgid ""
 "This will create a fat binary that works in both platforms, but will add "
 "about 6 megabytes to the APK."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:133
+#: ../../docs/development/compiling/compiling_for_android.rst:124
 msgid ""
 "It might be necessary to clean the build cache between two APK compilations, "
 "as some users have reported issues when building the two export templates "
 "one after the other."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:138
+#: ../../docs/development/compiling/compiling_for_android.rst:129
 msgid "Using the export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:140
+#: ../../docs/development/compiling/compiling_for_android.rst:131
 msgid ""
 "As export templates for Android, Godot needs release and debug APKs that "
 "were compiled against the same version/commit as the editor. If you are "
@@ -55492,40 +55691,40 @@ msgid ""
 "export templates, or to build your own from the same version."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:145
+#: ../../docs/development/compiling/compiling_for_android.rst:136
 msgid ""
 "When exporting your game, Godot opens the APK, changes a few things inside "
 "and adds your files."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:149
+#: ../../docs/development/compiling/compiling_for_android.rst:140
 msgid "Installing the templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:151
+#: ../../docs/development/compiling/compiling_for_android.rst:142
 msgid ""
 "The newly-compiled templates (android_debug.apk and android_release.apk) "
 "must be copied to Godot's templates folder with their respective names. The "
 "templates folder can be located in:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:155
+#: ../../docs/development/compiling/compiling_for_android.rst:146
 msgid ""
 "Windows: ``C:\\Users\\[username]\\AppData\\Roaming\\Godot\\templates"
 "\\[version]\\``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:156
+#: ../../docs/development/compiling/compiling_for_android.rst:147
 msgid "Linux: ``/home/[username]/.local/share/godot/templates/[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:157
+#: ../../docs/development/compiling/compiling_for_android.rst:148
 msgid ""
 "macOS: ``/Users/[username]/Library/Application Support/Godot/templates/"
 "[version]/``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:159
+#: ../../docs/development/compiling/compiling_for_android.rst:150
 msgid ""
 "``[version]`` is of the form ``major.minor[.patch].status`` using values "
 "from ``version.py`` in your Godot source repository (e.g. ``3.0.5.stable`` "
@@ -55533,131 +55732,131 @@ msgid ""
 "``version.txt`` file located next to your export templates."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:166
+#: ../../docs/development/compiling/compiling_for_android.rst:157
 msgid ""
 "However, if you are writing your custom modules or custom C++ code, you "
 "might instead want to configure your APKs as custom export templates here:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:172
+#: ../../docs/development/compiling/compiling_for_android.rst:163
 msgid ""
 "You don't even need to copy them, you can just reference the resulting file "
 "in the ``bin\\`` directory of your Godot source folder, so that the next "
 "time you build you will automatically have the custom templates referenced."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:181
+#: ../../docs/development/compiling/compiling_for_android.rst:172
 msgid "Application not installed"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:183
+#: ../../docs/development/compiling/compiling_for_android.rst:174
 msgid ""
 "Android might complain the application is not correctly installed. If so, "
 "check the following:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:186
+#: ../../docs/development/compiling/compiling_for_android.rst:177
 msgid "Check that the debug keystore is properly generated."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:187
+#: ../../docs/development/compiling/compiling_for_android.rst:178
 msgid "Check that jarsigner is from JDK 6, 7 or 8."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:189
+#: ../../docs/development/compiling/compiling_for_android.rst:180
 msgid "If it still fails, open a command line and run logcat:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:195
+#: ../../docs/development/compiling/compiling_for_android.rst:186
 msgid ""
 "And check the output while the application is installed. Reason for failure "
 "should be presented there."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:198
+#: ../../docs/development/compiling/compiling_for_android.rst:189
 msgid "Seek assistance if you can't figure it out."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:201
+#: ../../docs/development/compiling/compiling_for_android.rst:192
 msgid "Application exits immediately"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:203
+#: ../../docs/development/compiling/compiling_for_android.rst:194
 msgid ""
 "If the application runs but exits immediately, there might be one of the "
 "following reasons:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:206
+#: ../../docs/development/compiling/compiling_for_android.rst:197
 msgid ""
 "Make sure to use export templates that match your editor version; if you use "
 "a new Godot version, you *have* to update the templates too."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:208
+#: ../../docs/development/compiling/compiling_for_android.rst:199
 msgid "libgodot_android.so is not in ``lib/armeabi-v7a`` or ``lib/armeabi``"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:209
+#: ../../docs/development/compiling/compiling_for_android.rst:200
 msgid "Device does not support armv7 (try compiling yourself for armv6)"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:210
+#: ../../docs/development/compiling/compiling_for_android.rst:201
 msgid "Device is Intel, and apk is compiled for ARM."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:212
+#: ../../docs/development/compiling/compiling_for_android.rst:203
 msgid "In any case, ``adb logcat`` should also show the cause of the error."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:215
+#: ../../docs/development/compiling/compiling_for_android.rst:206
 msgid "Compilation fails"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:217
+#: ../../docs/development/compiling/compiling_for_android.rst:208
 msgid ""
 "On Linux systems with Kernel version 4.3 or newer, compilation may fail with "
 "the error \"pthread_create failed: Resource temporarily unavailable.\""
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:220
+#: ../../docs/development/compiling/compiling_for_android.rst:211
 msgid ""
 "This is because of a change in the way Linux limits thread creation. But you "
 "can change those limits through the command line. Please read this section "
 "thoroughly before beginning."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:224
+#: ../../docs/development/compiling/compiling_for_android.rst:215
 msgid ""
 "First open a terminal, then begin compilation as usual (it may be a good "
 "idea to run a --clean first). While compiling enter the following in your "
 "terminal:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:232
+#: ../../docs/development/compiling/compiling_for_android.rst:223
 msgid ""
 "The output should list a scons process, with its PID as the first number in "
 "the output. For example the PID 1077 in the output shown below:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:240
+#: ../../docs/development/compiling/compiling_for_android.rst:231
 msgid ""
 "Now you can use another command to increase the number of processes that "
 "scons is allowed to spawn. You can check its current limits with:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:247
+#: ../../docs/development/compiling/compiling_for_android.rst:238
 msgid "You can increase those limits with the command:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:253
+#: ../../docs/development/compiling/compiling_for_android.rst:244
 msgid ""
 "Obviously you should substitute the scons PID output by top and a limits "
 "that you think suitable. These are in the form --nproc=soft:hard where soft "
 "must be lesser than or equal to hard. See the man page for more information."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_android.rst:258
+#: ../../docs/development/compiling/compiling_for_android.rst:249
 msgid ""
 "If all went well, and you entered the prlimit command while scons was "
 "running, then your compilation should continue without the error."
@@ -55677,29 +55876,29 @@ msgstr ""
 msgid "Xcode with the iOS SDK and the command line tools."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:18
+#: ../../docs/development/compiling/compiling_for_ios.rst:21
 msgid "Open a Terminal, go to the root dir of the engine source code and type:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:24
+#: ../../docs/development/compiling/compiling_for_ios.rst:27
 msgid "for a debug build, or:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:30
+#: ../../docs/development/compiling/compiling_for_ios.rst:33
 msgid ""
 "for a release build (check ``platform/iphone/detect.py`` for the compiler "
 "flags used for each configuration)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:33
+#: ../../docs/development/compiling/compiling_for_ios.rst:36
 msgid "Alternatively, you can run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:39
+#: ../../docs/development/compiling/compiling_for_ios.rst:42
 msgid "for a Simulator executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:41
+#: ../../docs/development/compiling/compiling_for_ios.rst:44
 msgid ""
 "Additionally since some time Apple requires 64 bit version of application "
 "binary when you are uploading to iStore. The best way to provide these is to "
@@ -55710,17 +55909,17 @@ msgid ""
 "following commands:"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:53
+#: ../../docs/development/compiling/compiling_for_ios.rst:56
 msgid "Run"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:55
+#: ../../docs/development/compiling/compiling_for_ios.rst:58
 msgid ""
 "To run on a device or simulator, follow these instructions: :ref:"
 "`doc_exporting_for_ios`."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_ios.rst:58
+#: ../../docs/development/compiling/compiling_for_ios.rst:61
 msgid ""
 "Replace or add your executable to the Xcode project, and change the "
 "\"executable name\" property on Info.plist accordingly if you use an "
@@ -55830,6 +56029,10 @@ msgstr ""
 msgid "Pack the SDK:"
 msgstr ""
 
+#: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:101
+msgid "Toolchain"
+msgstr ""
+
 #: ../../docs/development/compiling/cross-compiling_for_ios_on_linux.rst:103
 msgid "Build cctools:"
 msgstr ""
@@ -55914,61 +56117,61 @@ msgid ""
 "(default) branch. Keep it in a path without spaces to avoid problems."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:23
+#: ../../docs/development/compiling/compiling_for_uwp.rst:26
 msgid ""
 "You need to open a proper Visual Studio prompt for the target architecture "
 "you want to build. Check :ref:`doc_compiling_for_windows` to see how these "
 "prompts work."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:27
+#: ../../docs/development/compiling/compiling_for_uwp.rst:30
 msgid ""
 "There are three target architectures for UWP: x86 (32-bits), x64 (64-bits) "
 "and ARM (32-bits). For the latter, you can run ``vcvarsall.bat`` with "
 "``x86_arm`` or ``amd64_arm`` as argument to set the environment."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:31
+#: ../../docs/development/compiling/compiling_for_uwp.rst:34
 msgid ""
 "Set the ``ANGLE_SRC_PATH`` to the directory where you downloaded the ANGLE "
 "source code. The build process will also build ANGLE to produce the required "
 "DLLs for the selected architecture."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:35
+#: ../../docs/development/compiling/compiling_for_uwp.rst:38
 msgid ""
 "Once you're set, run the SCons command similarly to the other platforms::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:40
+#: ../../docs/development/compiling/compiling_for_uwp.rst:43
 msgid "Creating UWP export templates"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:42
+#: ../../docs/development/compiling/compiling_for_uwp.rst:45
 msgid ""
 "To export using the editor you need to properly build package the templates. "
 "You need all three architectures with ``debug`` and ``release`` templates to "
 "be able to export."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:46
+#: ../../docs/development/compiling/compiling_for_uwp.rst:49
 msgid ""
 "Open the command prompt for one architecture and run SCons twice (once for "
 "each target)::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:52
+#: ../../docs/development/compiling/compiling_for_uwp.rst:55
 msgid "Repeat for the other architectures."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:54
+#: ../../docs/development/compiling/compiling_for_uwp.rst:57
 msgid ""
 "In the end your ``bin`` folder will have the ``.exe`` binaries with a name "
 "like ``godot.uwp.opt.debug.32.x86.exe`` (with variations for each target/"
 "arch)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:58
+#: ../../docs/development/compiling/compiling_for_uwp.rst:61
 msgid ""
 "Copy one of these to ``misc/dist/uwp_template`` inside the Godot source "
 "folder and rename the binary to ``godot.uwp.exe``. From the ANGLE source, "
@@ -55977,13 +56180,13 @@ msgid ""
 "putting them along with the executable."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:64
+#: ../../docs/development/compiling/compiling_for_uwp.rst:67
 msgid ""
 "Add the files in the ``uwp_template`` folder to a ZIP. Rename the resulting "
 "Zip according to the target/architecture of the template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:74
+#: ../../docs/development/compiling/compiling_for_uwp.rst:77
 msgid ""
 "Move those templates to the ``[versionstring]\\templates`` folder in Godot "
 "settings path, where `versionstring` is the version of Godot you have "
@@ -55992,11 +56195,11 @@ msgid ""
 "\"Custom Package\" property in the export window."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:81
+#: ../../docs/development/compiling/compiling_for_uwp.rst:84
 msgid "Running UWP apps with Visual Studio"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:83
+#: ../../docs/development/compiling/compiling_for_uwp.rst:86
 msgid ""
 "If you want to debug the UWP port or simply run your apps without packaging "
 "and signing, you can deploy and launch them using Visual Studio. It might be "
@@ -56004,14 +56207,14 @@ msgid ""
 "Xbox One."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:88
+#: ../../docs/development/compiling/compiling_for_uwp.rst:91
 msgid ""
 "Within the ANGLE source folder, open ``templates`` and double-click the "
 "``install.bat`` script file. This will install the Visual Studio project "
 "templates for ANGLE apps."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:92
+#: ../../docs/development/compiling/compiling_for_uwp.rst:95
 msgid ""
 "If you have not built Godot yet, open the ``winrt/10/src/angle.sln`` "
 "solution from the ANGLE source and build it to Release/Win32 target. You may "
@@ -56019,14 +56222,14 @@ msgid ""
 "use MSBuild if you're comfortable with the command line."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:97
+#: ../../docs/development/compiling/compiling_for_uwp.rst:100
 msgid ""
 "Create a new Windows App project using the \"App for OpenGL ES (Windows "
 "Universal)\" project template, which can be found under the ``Visual C++/"
 "Windows/Universal`` category."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:101
+#: ../../docs/development/compiling/compiling_for_uwp.rst:104
 msgid ""
 "This is a base project with the ANGLE dependencies already set up. However, "
 "by default it picks the debug version of the DLLs which usually have poor "
@@ -56035,14 +56238,14 @@ msgid ""
 "``Debug_Win32`` to ``Release_Win32`` (or ``Release_ARM`` for devices)."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:107
+#: ../../docs/development/compiling/compiling_for_uwp.rst:110
 msgid ""
 "In the same \"Binaries\" filter, select \"Add > Existing Item\" and point to "
 "the Godot executable for UWP you have. In the \"Properties\" window, set "
 "\"Content\" to ``True`` so it's included in the project."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:111
+#: ../../docs/development/compiling/compiling_for_uwp.rst:114
 msgid ""
 "Right-click the ``Package.appxmanifest`` file and select \"Open With... > "
 "XML (Text) Editor\". In the ``Package/Applications/Application`` element, "
@@ -56052,7 +56255,7 @@ msgid ""
 "Godot executable is correctly called when the app starts."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:118
+#: ../../docs/development/compiling/compiling_for_uwp.rst:121
 msgid ""
 "Create a folder (*not* a filter) called ``game`` in your Visual Studio "
 "project folder and there you can put either a ``data.pck`` file or your "
@@ -56061,7 +56264,7 @@ msgid ""
 "they're copied to the app."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:124
+#: ../../docs/development/compiling/compiling_for_uwp.rst:127
 msgid ""
 "To ease the workflow, you can open the \"Solution Properties\" and in the "
 "\"Configuration\" section untick the \"Build\" option for the app. You still "
@@ -56070,7 +56273,7 @@ msgid ""
 "\" and selecting \"Build\"."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_uwp.rst:130
+#: ../../docs/development/compiling/compiling_for_uwp.rst:133
 msgid ""
 "Now you can just run the project and your app should open. You can use also "
 "the \"Start Without Debugging\" from the \"Debug\" menu (Ctrl+F5) to make it "
@@ -56101,7 +56304,7 @@ msgstr ""
 msgid "`SCons <https://www.scons.org>`__ build system"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:22
+#: ../../docs/development/compiling/compiling_for_web.rst:25
 msgid ""
 "Before starting, confirm that the Emscripten configuration file exists and "
 "specifies all settings correctly. This file is available as ``~/."
@@ -56111,7 +56314,7 @@ msgid ""
 "when starting Emscripten's ``emcc`` program if the file doesn't exist."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:29
+#: ../../docs/development/compiling/compiling_for_web.rst:32
 msgid ""
 "Open a terminal and navigate to the root directory of the engine source "
 "code. Then instruct SCons to build the JavaScript platform. Specify "
@@ -56119,14 +56322,14 @@ msgid ""
 "for a debug build::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:36
+#: ../../docs/development/compiling/compiling_for_web.rst:39
 msgid ""
 "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be "
 "built into the engine. Since ``eval()`` calls can be a security concern, the "
 "``javascript_eval`` option can be used to build without the singleton::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:43
+#: ../../docs/development/compiling/compiling_for_web.rst:46
 msgid ""
 "The engine will now be compiled to WebAssembly by Emscripten. Once finished, "
 "the resulting file will be placed in the ``bin`` subdirectory. Its name is "
@@ -56134,21 +56337,21 @@ msgid ""
 "zip`` for debug."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:48
+#: ../../docs/development/compiling/compiling_for_web.rst:51
 msgid ""
 "Finally, rename the zip archive to ``webassembly_release.zip`` for the "
 "release template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:53
+#: ../../docs/development/compiling/compiling_for_web.rst:56
 msgid "And ``webassembly_debug.zip`` for the debug template::"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:58
+#: ../../docs/development/compiling/compiling_for_web.rst:61
 msgid "Building per asm.js translation or LLVM backend"
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:60
+#: ../../docs/development/compiling/compiling_for_web.rst:63
 msgid ""
 "WebAssembly can be compiled in two ways: The default is to first compile to "
 "asm.js, a highly optimizable subset of JavaScript, using Emscripten's "
@@ -56157,7 +56360,7 @@ msgid ""
 "processes, we simply run SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:66
+#: ../../docs/development/compiling/compiling_for_web.rst:69
 msgid ""
 "The other method uses LLVM's WebAssembly backend. This backend is not yet "
 "available in release versions of LLVM, only in development builds built with "
@@ -56167,7 +56370,7 @@ msgid ""
 "processes as well, so we just invoke SCons."
 msgstr ""
 
-#: ../../docs/development/compiling/compiling_for_web.rst:73
+#: ../../docs/development/compiling/compiling_for_web.rst:76
 msgid ""
 "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the "
 "Emscripten configuration file is used. If it points to a directory "