[gedit] docs: gedit-development-getting-started: small improvements

[Sébastien Wilmet <swilmet src gnome org>]

commit 5d2620df8b3c924762f23b95405635b43325adcd
Author: Sébastien Wilmet <swilmet gnome org>
Date:   Tue Aug 27 18:34:34 2019 +0200

    docs: gedit-development-getting-started: small improvements

 docs/gedit-development-getting-started.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)
---
diff --git a/docs/gedit-development-getting-started.md b/docs/gedit-development-getting-started.md
index 158ca2696..fff96013e 100644
--- a/docs/gedit-development-getting-started.md
+++ b/docs/gedit-development-getting-started.md
@@ -2,7 +2,7 @@ gedit development - getting started
 ===================================
 
 The following explanations can be improved over time, if you see something
-missing.
+missing, a feedback is welcome.
 
 Programming languages and paradigms
 -----------------------------------
@@ -88,7 +88,8 @@ To find something interesting to do, […]. TODO: provide list of easy tasks in
 gedit itself.
 
 A good way to learn a lot of things is to write a new plugin (as a third-party
-plugin first). TODO: provide list of new plugins ideas.
+plugin first). To have some inspiration, see the wiki page
+[RequestedPlugins](https://wiki.gnome.org/Apps/Gedit/RequestedPlugins).
 
 A potentially easy task (but not always) is to fix compilation warnings, for
 example when a deprecated function is used. If you encounter a runtime warning