fix RST warnings

1 files changed, 18 insertions, 13 deletions

diff --git a/developers-manual.rst b/developers-manual.rst
index 8c3a3501..6e0bc309 100644
--- a/developers-manual.rst
+++ b/developers-manual.rst
@@ -28,7 +28,7 @@ Developer's Manual
 
 .. note::
 
-  This manual contains information for developers working on GNU Taler 
+  This manual contains information for developers working on GNU Taler
   and related components.  It is not intended for a general audience.
 
 .. contents:: Table of Contents
@@ -636,13 +636,13 @@ About Privilege Levels
 
 This is the breakdown of privilege levels in Weblate:
 
-* **Users**/**Viewers** = Can log in, view Translations  (*applies to new users*)
+  * **Users**/**Viewers** = Can log in, view Translations  (*applies to new users*)
 
-* **Reviewers** = Can contribute Translations to existing *Components*
+  * **Reviewers** = Can contribute Translations to existing *Components*
 
-* **Managers** = Can create new *Components* of existing *Projects*
+  * **Managers** = Can create new *Components* of existing *Projects*
 
-* **Superusers** = Can create new *Projects*
+  * **Superusers** = Can create new *Projects*
 
 Upgrading Privileges
 --------------------
@@ -661,20 +661,25 @@ Reference: https://docs.weblate.org/en/weblate-4.0.3/admin/projects.html#compone
 
 In Weblate, a *Component* is a subset of a *Project* and each Component contains N translations.  A Component is generally associated with a Git repo.
 
-To create a Component, log into https://weblate.taler.net/ with your *Manager* or higher credentials and choose **+ Add* from the upper-right corner.
+To create a Component, log into https://weblate.taler.net/ with your *Manager* or higher credentials and choose **+ Add** from the upper-right corner.
 
 What follows is a sort of Wizard.  You can find detailed docs at https://docs.weblate.org/.  Here are some important notes about connecting your Component to the Taler Git repository:
 
 Under *https://weblate.taler.net/create/component/vcs/*:
 
-* **Source code repository** - Generally ``git+ssh://git@git.taler.net/<reponame>```.  Check with ``git remote -v``.
-* **Repository branch** - Choose the correct branch to draw from and commit to.
-* **Repository push URL** - This is generally ``git+ssh://git@git.taler.net/<reponame>```  Check with ``git remote -v``.
-* **Repository browser** - This is the www URL of the Git repo's file browser.  Example ``https://git.taler.net/<repositoryname>.git/tree/{{filename}}?h={{branch}}#n{{line}}`` where ``<repositoryname>`` gets replaced but ``{{filename}}`` and other items in braces are actual variables in the string.
-* **Merge style** - *Rebase*, in line with GNU Taler development procedures
+  * **Source code repository** - Generally ``git+ssh://git@git.taler.net/<reponame>```.  Check with ``git remote -v``.
 
-* **Translation license** - *GNU General Public License v3.0 or Later*
-* **Adding new translation** - Decide how to handle adding new translations
+  * **Repository branch** - Choose the correct branch to draw from and commit to.
+
+  * **Repository push URL** - This is generally ``git+ssh://git@git.taler.net/<reponame>```  Check with ``git remote -v``.
+
+  * **Repository browser** - This is the www URL of the Git repo's file browser.  Example ``https://git.taler.net/<repositoryname>.git/tree/{{filename}}?h={{branch}}#n{{line}}`` where ``<repositoryname>`` gets replaced but ``{{filename}}`` and other items in braces are actual variables in the string.
+
+  * **Merge style** - *Rebase*, in line with GNU Taler development procedures
+
+  * **Translation license** - *GNU General Public License v3.0 or Later*
+
+  * **Adding new translation** - Decide how to handle adding new translations
 
 How to Create a Translation
 ---------------------------