RMA as an APP

rma/README.rst

@@ -1,6 +1,3 @@
-.. image:: https://img.shields.io/badge/licence-LGPL--3-blue.svg
-    :alt: License LGPL-3
-
 ======================================
 RMA (Return Merchandise Authorization)
 ======================================
@@ -24,12 +21,16 @@ of the product to the manufacturer, commonly referred to as a return.
 As returns are costly for the vendor and inconvenient for the customer,
 any return that can be prevented benefits both parties.
 
+**Table of contents**
+
+.. contents::
+   :local:
 
 Configuration
 =============
 
 Security
---------
+~~~~~~~~
 
 Go to Settings > Users and assign the appropiate permissions to users.
 Different security groups grant distinct levels of access to the RMA features.
@@ -41,7 +42,7 @@ Different security groups grant distinct levels of access to the RMA features.
   associated to both customers and suppliers.
 
 RMA Approval Policy
--------------------
+~~~~~~~~~~~~~~~~~~~
 
 There are two RMA approval policies in product catogories:
 
@@ -57,12 +58,12 @@ steps:
 #. Select one and change the field *RMA Approval Policy* to your convenience.
 
 Other Settings
---------------
+~~~~~~~~~~~~~~
 
-#. Go to Inventory > Configuration > Settings > Return Merchandising
+#. Go to RMA > Configuration > Settings > Return Merchandising
    Authorization and select the option "Display 3 fields on rma: partner,
    invoice address, delivery address" if needed.
-#. Go to Inventory > Configuration > Warehouse management > Warehouses and add
+#. Go to RMA > Configuration > Warehouse management > Warehouses and add
    a default RMA location and RMA picking type for customers and suppliers RMA
    picking type. In case the warehouse is configured to use routes, you need to
    create at least one route per rma type with at least two push rules (one for
@@ -86,8 +87,8 @@ Create an RMA:
    Order".
 #. Go back to the RMA. Set the RMA to done if not further action is required.
 
-Known issues and Roadmap
-========================
+Known issues / Roadmap
+======================
 
 * Picking operations report in customer RMA dropshipping case is showing
   "Vendor Address" while it should be "Customer Address".
@@ -99,27 +100,37 @@ Known issues and Roadmap
 Bug Tracker
 ===========
 
-Bugs are tracked on `GitHub Issues
-<https://github.com/ForgeFlow/stock-rma/issues>`_. In case of trouble, please
-check there if your issue has already been reported. If you spotted it first,
-help us smashing it by providing a detailed and welcomed feedback.
+Bugs are tracked on `GitHub Issues <https://github.com/ForgeFlow/stock-rma/issues>`_.
+In case of trouble, please check there if your issue has already been reported.
+If you spotted it first, help us smashing it by providing a detailed and welcomed
+`feedback <https://github.com/ForgeFlow/stock-rma/issues/new?body=module:%20rma%0Aversion:%2013.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>`_.
 
+Do not contact contributors directly about support or help with technical issues.
 
 Credits
 =======
 
-Contributors
-------------
+Authors
+~~~~~~~
 
-* Jordi Ballester Alomar <jordi.ballester@ForgeFlow.com>
-* Aaron Henriquez <ahenriquez@ForgeFlow.com>
-* Lois Rilo <lois.rilo@ForgeFlow.com>
+* ForgeFlow S.L.
+
+Contributors
+~~~~~~~~~~~~
+
+* Jordi Ballester Alomar <jordi.ballester@forgeflow.com>
+* Aaron Henriquez <ahenriquez@forgeflow.com>
+* Lois Rilo <lois.rilo@forgeflow.com>
 * Bhavesh Odedra <bodedra@opensourceintegrators.com>
 * Akim Juillerat <akim.juillerat@camptocamp.com>
 * Alexandre Fayolle <alexandre.fayolle@camptocamp.com>
 * Chafique Delli <chafique.delli@akretion.com>
+* Héctor Villarreal <hector.villarreal@forgeflow.com>
 
-Maintainer
-----------
+Maintainers
+~~~~~~~~~~~
+
+This module is maintained by the ForgeFlow.
+
+This module is part of the `ForgeFlow/stock-rma <https://github.com/ForgeFlow/stock-rma/tree/13.0/rma>`_ project on GitHub.
 
-This module is maintained by ForgeFlow.