docs: Updated some 'Future extensions' items

* Projects are accessible through scripting API, though the custom types
  are not.

* Wrong file paths in templates are already handled.

docs/manual/projects.rst

@@ -70,8 +70,8 @@ just type the name of the file you'd like to open.
 
    There are many ways in which the projects could be made more powerful:
 
-   -  Make the project accessible through the :doc:`scripting API
-      </manual/scripting>`.
+   -  Make the custom types defined in the project accessible through the
+      :doc:`scripting API </manual/scripting>` (`#3419 <https://github.com/mapeditor/tiled/issues/3419>`__).
 
    -  Allow turning off features on a per-project basis, to simplify the UI
       and reduce the chance of accidentally doing something your project

docs/manual/using-templates.rst

@@ -106,6 +106,5 @@ use them, you can enable the *Detach templates* :ref:`export option
 
     - Resetting overridden properties individually (`#1725 <https://github.com/bjorn/tiled/issues/1725>`__).
     - Locking template properties (`#1726 <https://github.com/bjorn/tiled/issues/1726>`__).
-    - Handling wrong file paths (`#1732 <https://github.com/bjorn/tiled/issues/1732>`__).
     - Managing the templates folder, e.g. moving, renaming or deleting a template or a sub-folder
       (`#1723 <https://github.com/bjorn/tiled/issues/1723>`__).