Context Navigation

Changes between Version 1 and Version 4 of Ticket #2921

-                      v1
+                      v4
 * If the plugin already has a language pack, there's another notice: `This plugin is also available in [language name].` The link leads to the plugin page on the corresponding Rosetta site, which might seem like a good idea, but there's no longer a call to improve the translation.
 It's still possible to go to the translation project from the plugin page, but the way to do that is a bit convoluted and isn't obvious for a translator at all:
+It's still possible to go to the translation project from the plugin page, but the way to do that is a bit convoluted and isn't obvious for a translator at all. There's a good chance they won't find the link unless they already know where to look:
 . Click "Development" tab.
 . Click "Read more" link.
+. Click "Translate [plugin name] into your language."
 Suggestion: Add a call to improve the translation to the second notice: `This plugin is also available in [language name]. <a href="%s">Help improve the translation!</a>`.