Improve documentation clarity in plugin publishing guidelines

Author: Xpirix

qgis-app/templates/flatpages/docs_publish.html

@@ -19,8 +19,15 @@ <h4>Requirements</h4>
   <ul>
     <li>Plugins need to have at least minimal documentation</li>
     <li>
-      The plugin metadata contains a valid link to the homepage, the repository
-      (source code), the tracker (issue tracker) and a license
+      The plugin metadata contains a valid link to the homepage
+      (the URL should either point to a page describing plugin
+      usage or the README/wiki in your repository),
+      the repository (source code - should be publicly accessible
+      and should not contain zipped files),
+      the tracker (issue tracker) and a license.
+    </li>
+    <li>
+      All plugins should include a short English description of what the plugin does.
     </li>
     <li>
       The plugin license is compatible with the
@@ -39,7 +46,7 @@ <h4>Requirements</h4>
     <li>
       If the plugin has an external dependency, this needs to be clearly stated
       in the About metadata field; you can include a short guide to install
-      Python libs as needed, or opint to existing guides, e.g. for Windows:
+      Python libs as needed, or point to existing guides, e.g. for Windows:
       "<a href="https://landscapearchaeology.org/2018/installing-python-packages-in-qgis-3-for-windows/"
          >Installing Python packages in QGIS 3 (for Windows)</a>"
     </li>
@@ -61,7 +68,7 @@ <h4>Recommendations</h4>
       functionality and explore collaboration possibilities
     </li>
     <li>
-      Make your plugin work on all supported platforms (Windows, Linux, macOs)
+      Make your plugin work on all supported platforms (Windows, Linux, macOS)
     </li>
     <li>
       Don't rename the plugin title just because it's upgraded to a newer