Added download link and other fixes to "Exporting projects"

tutorials/asset_pipeline/exporting_projects.rst

@@ -19,7 +19,7 @@ On PC
 
 Distributing a game project on PC with Godot is rather easy. Just drop
 the godot.exe (or godot) binary together in the same place as the
-engine.cfg file, zip it and you are done. This can be taken advantage to
+engine.cfg file, zip it and you are done. This can be taken advantage of to
 make custom installers.
 
 It sounds simple, but there are probably a few reasons why the developer
@@ -30,7 +30,7 @@ etc.
 
 Another reason is that, for distribution, the developer might use a
 specially compiled binary, which is smaller in size, more optimized and
-does not include tools inside (like the editor, debugger, etc).
+does not include tools inside (like the editor, debugger, etc.).
 
 Finally, Godot has a simple but efficient system for creating DLCs as
 extra package files.
@@ -52,16 +52,16 @@ different devices prefer some data in different formats to run. The main
 example of this is texture compression. All PC hardware uses S3TC (BC)
 compression and that has been standardized for more than a decade, but
 mobile devices use different formats for texture compression, such as
-PVRCT (iOS) or ETC (Android)
+PVRCT (iOS) or ETC (Android).
 
 Export dialog
 -------------
 
 After many attempts at different export workflows, the current one has
-worked the best. At the time of this writing, not all platforms are
-supported yet, but that will change soon.
+proven to work the best. At the time of this writing, not all platforms are
+supported yet, but the supported platforms continue to grow.
 
-To open the export dialog, just click the "Export" Button:
+To open the export dialog, just click the "Export" button:
 
 .. image:: /img/export.png
 
@@ -70,23 +70,24 @@ The dialog will open, showing all the supported export platforms:
 .. image:: /img/export_dialog.png
 
 The default options are often enough to export, so tweaking them is not
-necessary until it's needed. However, many platforms require additional
+necessary, but provide extra control. However, many platforms require additional
 tools (SDKs) to be installed to be able to export. Additionally, Godot
 needs exports templates installed to create packages. The export dialog
 will complain when something is missing and will not allow the user to
-export for that platform until he or she resolves it:
+export for that platform until they resolve it:
 
 .. image:: /img/export_error.png
 
-At that time, the user is expected to come back to the wiki and follow
+At that time, the user is expected to come back to the documentation and follow
 instructions on how to properly set up that platform.
 
 Export templates
 ~~~~~~~~~~~~~~~~
 
 Apart from setting up the platform, the export templates must be
-installed to be able to export projects. They can be downloaded as a
-.tpz (a renamed .zip) file from the wiki.
+installed to be able to export projects. They can be obtained as a
+.tpz (a renamed .zip) file from the `download page of the website
+<https://www.godotengine.org/download>`_.
 
 Once downloaded, they can be installed using the "Install Export
 Templates" option in the editor:
@@ -108,12 +109,12 @@ creates the package. There are 3 different modes for exporting:
 -  **Export every single file** - This mode exports every single file in
    the project. This is good to test if something is being forgotten,
    but developers often have a lot of unrelated stuff around in the dev
-   dir, which makes it a bad idea.
+   directory, which makes it a bad idea.
 
 -  **Export only resources** - Only resources are exported. For most
    projects, this is enough. However many developers like to use custom
    datafiles in their games. To compensate for this, filters can be
-   added for extra extensions (like, *.txt,*.csv, etc).
+   added for extra extensions (like, *.txt,*.csv, etc.).
 
 -  **Export only selected resources** - Only select resources from a
    list are exported. This is probably overkill for most projects, but