[FIX] *: RST cleanup

RST cleanup to comply with the RST guidelines. This is required so we
can use "make test", as there are currently hundreds of errors. For now,
it is unusable because of the oldest code in this repo.

closes odoo/documentation#3584

Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>

content/developer/reference/backend/actions.rst

@@ -408,7 +408,7 @@ how the POS interface works.
 .. _reference/actions/cron:
 
 Automated Actions (``ir.cron``)
-======================================
+===============================
 
 Actions triggered automatically on a predefined frequency.
 

content/developer/reference/backend/data.rst

@@ -77,7 +77,7 @@ following attributes:
     Requires an :term:`external id`, defaults to ``True``.
 
 ``field``
-----------
+---------
 
 Each record can be composed of ``field`` tags, defining values to set when
 creating the record. A ``record`` with no ``field`` will use all default

content/developer/reference/backend/mixins.rst

@@ -20,7 +20,7 @@ Messaging integration
 ---------------------
 
 Basic messaging system
-''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~
 
 Integrating messaging features to your model is extremely easy. Simply inheriting
 the ``mail.thread`` model and adding the messaging fields (and their appropriate
@@ -192,9 +192,8 @@ a date or an e-mail address, add CC's addresses as followers, etc.).
     :return: True
     :rtype: bool
 
-
 Logging changes
-'''''''''''''''
+~~~~~~~~~~~~~~~
 
 The ``mail`` module adds a powerful tracking system on fields, allowing you
 to log changes to specific fields in the record's chatter. To add tracking
@@ -221,9 +220,8 @@ to a field, simple set the tracking attribute to True.
     well to give more context about the notification (even if the name did not
     change).
 
-
 Subtypes
-''''''''
+~~~~~~~~
 
 Subtypes give you more granular control over messages. Subtypes act as a classification
 system for notifications, allowing subscribers to a document to customize the
@@ -318,9 +316,8 @@ can override the ``_track_subtype()`` function:
                     return self.env.ref('my_module.mt_state_change')
                 return super(BusinessTrip, self)._track_subtype(init_values)
 
-
 Customizing notifications
-'''''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~~~~
 
 When sending notifications to followers, it can be quite useful to add buttons in
 the template to allow quick actions directly from the e-mail. Even a simple button
@@ -469,7 +466,7 @@ The urls in the actions list can be generated automatically by calling the
     that can sometimes be boring, I choose the former instead of the latter.
 
 Overriding defaults
-'''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~
 
 There are several ways you can customize the behaviour of ``mail.thread`` models,
 including (but not limited to):
@@ -510,7 +507,7 @@ the outside, allowing users or customers to quickly create records in your
 database without needing to connect to Odoo directly.
 
 Aliases vs. Incoming Mail Gateway
-'''''''''''''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Some people use the Incoming Mail Gateway for this same purpose. You still need
 a correctly configured mail gateway to use aliases, however a single
@@ -531,7 +528,7 @@ Aliases have several advantages over Mail Gateways:
 
 
 Alias support integration
-'''''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Aliases are usually configured on a parent model which will then create specific
 record when contacted by e-mail. For example, Project have aliases to create tasks
@@ -977,7 +974,7 @@ The rating mixin allows sending email to ask for customer rating, automatic
 transitioning in a kanban processes and aggregating statistics on your ratings.
 
 Adding rating on your model
-'''''''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 To add rating support, simply inherit the ``rating.mixin`` model:
 
@@ -1010,7 +1007,7 @@ The behaviour of the mixin adapts to your model:
   ``mail.thread``)
 
 Send rating requests by e-mail
-''''''''''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 If you wish to send emails to request a rating, simply generate an e-mail with
 links to the rating object. A very basic email template could look like this:

content/developer/reference/backend/orm.rst

@@ -153,7 +153,7 @@ Advanced Fields
 .. _reference/fields/date:
 
 Date(time) Fields
-'''''''''''''''''
+~~~~~~~~~~~~~~~~~
 
 :class:`Dates <odoo.fields.Date>` and :class:`Datetimes <odoo.fields.Datetime>`
 are very important fields in any kind of business application.
@@ -214,7 +214,7 @@ These helpers are also available by importing `odoo.tools.date_utils`.
 .. _reference/fields/relational:
 
 Relational Fields
-'''''''''''''''''
+~~~~~~~~~~~~~~~~~
 
 .. autoclass:: Many2one()
 
@@ -228,7 +228,7 @@ Relational Fields
    :member-order: bysource
 
 Pseudo-relational fields
-''''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. autoclass:: Reference()
 
@@ -237,7 +237,7 @@ Pseudo-relational fields
 .. _reference/fields/compute:
 
 Computed Fields
-'''''''''''''''
+~~~~~~~~~~~~~~~
 
 Fields can be computed (instead of read straight from the database) using the
 ``compute`` parameter. **It must assign the computed value to the field**. If
@@ -328,7 +328,7 @@ it uses the values of other *fields*, it should specify those fields using
 .. _reference/fields/related:
 
 Related fields
-''''''''''''''
+~~~~~~~~~~~~~~
 
 A special case of computed fields are *related* (proxy) fields, which provide
 the value of a sub-field on the current record. They are defined by setting
@@ -410,7 +410,7 @@ Automatic fields
 .. _reference/fields/automatic/log_access:
 
 Access Log fields
-'''''''''''''''''
+~~~~~~~~~~~~~~~~~
 
 These fields are automatically set and updated if
 :attr:`~odoo.models.BaseModel._log_access` is enabled. It can be
@@ -472,10 +472,10 @@ behavior is desired:
   .. automethod:: Model.action_unarchive
 
 .. .. attribute:: sequence
-..
+
 ..   Alterable ordering criteria, allows drag-and-drop reordering of models
 ..   in list views.
-..
+
 ..   :class:`~odoo.fields.Integer`
 
 .. attribute:: Model.state
@@ -852,14 +852,14 @@ Search/Read
 .. automethod:: Model.read_group
 
 Fields
-''''''
+~~~~~~
 
 .. automethod:: Model.fields_get
 
 .. _reference/orm/domains:
 
 Search domains
-''''''''''''''
+~~~~~~~~~~~~~~
 
 A domain is a list of criteria, each criterion being a triple (either a
 ``list`` or a ``tuple``) of ``(field_name, operator, value)`` where:
@@ -1021,14 +1021,14 @@ Recordsets therefore provide the following operations returning recordsets thems
 (when possible):
 
 Filter
-''''''
+~~~~~~
 
 .. automethod:: Model.filtered
 
 .. automethod:: Model.filtered_domain
 
 Map
-'''
+~~~
 
 .. automethod:: Model.mapped
 
@@ -1043,12 +1043,12 @@ Map
         records.partner_id.mapped('name')  # == records.mapped('partner_id.name')
 
 Sort
-''''
+~~~~
 
 .. automethod:: Model.sorted
 
 Grouping
-''''''''
+~~~~~~~~
 
 .. automethod:: Model.grouped
 

content/developer/reference/backend/orm/changelog.rst

@@ -5,7 +5,7 @@ Changelog
 =========
 
 Odoo version 16.0
-========================
+=================
 
 - Translations for translated fields are stored as JSONB values with
   `#97692 <https://github.com/odoo/odoo/pull/97692>`_

content/developer/reference/backend/reports.rst

@@ -164,6 +164,7 @@ More parameters can be passed as a query string
 
 Useful Remarks
 --------------
+
 * Twitter Bootstrap and FontAwesome classes can be used in your report
   template
 * Local CSS can be put directly in the template
@@ -277,6 +278,7 @@ the template, such as data from additional models:
 
 Custom fonts
 ============
+
 If you want to use custom fonts you will need to add your custom font and the related less/CSS to the ``web.reports_assets_common`` assets bundle.
 Adding your custom font(s) to ``web.assets_common`` or ``web.assets_backend`` will not make your font available in QWeb reports.
 

content/developer/reference/backend/security.rst

@@ -225,6 +225,7 @@ properly.
 
 Bypassing the ORM
 -----------------
+
 You should never use the database cursor directly when the ORM can do the same
 thing! By doing so you are bypassing all the ORM features, possibly the
 automated behaviours like translations, invalidation of fields, ``active``,
@@ -250,6 +251,7 @@ less secure.
 
 SQL injections
 ~~~~~~~~~~~~~~
+
 Care must be taken not to introduce SQL injections vulnerabilities when using
 manual SQL queries. The vulnerability is present when user input is either
 incorrectly filtered or badly quoted, allowing an attacker to introduce
@@ -420,6 +422,7 @@ likely it is to break things.
 
 Evaluating content
 ------------------
+
 Some may want to ``eval`` to parse user provided content. Using ``eval`` should
 be avoided at all cost. A safer, sandboxed, method :class:`~odoo.tools.safe_eval`
 can be used instead but still gives tremendous capabilities to the user running

content/developer/reference/backend/testing.rst

@@ -1,9 +1,8 @@
 .. _reference/testing:
 
-
-===============
+============
 Testing Odoo
-===============
+============
 
 There are many ways to test an application.  In Odoo, we have three kinds of
 tests
@@ -734,7 +733,8 @@ Observing tours in a browser
 There are two ways with different tradeoffs:
 
 ``watch=True``
-''''''''''''''
+**************
+
 When running a tour locally via the test suite, the ``watch=True``
 parameter can be added to the ``browser_js`` or ``start_tour``
 call::
@@ -753,7 +753,8 @@ run inside it.
   - only works if the test / tour can run correctly locally
 
 Run via browser
-'''''''''''''''
+***************
+
 Tours can also be launched via the browser UI, either by calling
 
 .. code-block:: javascript

content/developer/reference/backend/views.rst

@@ -337,7 +337,7 @@ A view's specs are applied sequentially.
                all the specified classes
 
 Model Commons
-====================
+=============
 
 .. currentmodule:: odoo.addons.base.models.ir_ui_view
 
@@ -348,6 +348,7 @@ Attributes
 
 Methods
 -------
+
 .. automethod:: Model.get_views
 .. automethod:: Model.get_view
 

content/developer/reference/frontend/javascript_cheatsheet.rst

@@ -280,12 +280,13 @@ using the view in the kanban arch (a specific example is the helpdesk dashboard)
     need to have a valid arch field.
 
 Promises and asynchronous code
-===============================
+==============================
 
 For a very good and complete introduction to promises, please read this excellent article https://github.com/getify/You-Dont-Know-JS/blob/1st-ed/async%20%26%20performance/ch3.md
 
 Creating new Promises
------------------------
+---------------------
+
 - turn a constant into a promise
     There are 2 static functions on Promise that create a resolved or rejected promise based on a constant:
 
@@ -383,6 +384,7 @@ Creating new Promises
 
 Waiting for Promises
 --------------------
+
 - waiting for a number of Promises
         if you have multiple promises that all need to be waited, you can convert them into a single promise that will be resolved when all the promises are resolved using Promise.all(arrayOfPromises).
 
@@ -486,7 +488,7 @@ Error handling
 
 
 Testing asynchronous code
---------------------------
+-------------------------
 
 - using promises in tests
         In the tests code, we support the latest version of Javascript, including primitives like `async` and `await`. This makes using and waiting for promises very easy.

content/developer/reference/frontend/javascript_modules.rst

@@ -263,7 +263,7 @@ within the same Odoo addon.
 .. _frontend/modules/odoo_module:
 
 Odoo Module System
-===================
+==================
 
 Odoo has defined a small module system (located in the file
 :file:`addons/web/static/src/js/boot.js`, which needs to be loaded first). The Odoo
@@ -371,7 +371,7 @@ If an error happens, it will be logged (in debug mode) in the console:
   Modules who depend on a missing or a failed module
 
 Asynchronous modules
----------------------
+--------------------
 
 It can happen that a module needs to perform some work before it is ready.  For
 example, it could do an rpc to load some data.  In that case, the module can

content/developer/reference/frontend/javascript_reference.rst

@@ -1,11 +1,10 @@
-
 .. highlight:: javascript
 
 .. default-domain:: js
 
-=====================
+====================
 Javascript Reference
-=====================
+====================
 
 This document presents the Odoo Javascript framework. This
 framework is not a large application in term of lines of code, but it is quite
@@ -15,7 +14,7 @@ records in the database.  It is even possible to use the web client to modify
 the interface of the web client.
 
 Overview
-=========
+========
 
 The Javascript framework is designed to work with three main use cases:
 
@@ -53,7 +52,7 @@ action manager) actually creates and destroys many sub components. The state is
 highly dynamic, and each widget could be destroyed at any time.
 
 Overview of web client JS code
--------------------------------------
+------------------------------
 
 Here, we give a very quick overview on the web client code, in
 the *web/static/src/js* addon. Note that it is deliberately not exhaustive.
@@ -105,7 +104,7 @@ are a few things you can try to solve the issue:
 
 
 Loading Javascript Code
-========================
+=======================
 
 Large applications are usually broken up into smaller files, that need to be
 connected together.  Some file may need to use some part of code defined in
@@ -146,8 +145,6 @@ not the primary way to write javascript code.
 .. note::
     Native javascript modules are the primary way to define javascript code.
 
-
-
 Class System
 ============
 
@@ -204,7 +201,6 @@ framework will secretly rebind a special method: *_super* to the currently
 called method.  This allows us to use *this._super* whenever we need to call a
 parent method.
 
-
 .. code-block:: javascript
 
     var Animal = require('web.Animal');
@@ -248,7 +244,6 @@ of them in the new class.
 In this example, the *Hamster* class is a subclass of Animal, but it also mix
 the DanceMixin in.
 
-
 Patching an existing class
 --------------------------
 
@@ -273,7 +268,6 @@ the way Odoo is structured, it is sometimes necessary in one addon to modify
 the behavior of a widget/class defined in another addon.  Note that it will
 modify all instances of the class, even if they have already been created.
 
-
 Widgets
 =======
 
@@ -524,7 +518,6 @@ Widget API
     :param Element element: a DOM element or jQuery object to set as
                             the widget's DOM root
 
-
 Inserting a widget in the DOM
 -----------------------------
 
@@ -558,7 +551,7 @@ and are charged with three tasks:
 * starting the widget, and returning the result of starting it
 
 Widget Guidelines
-----------------------
+-----------------
 
 * Identifiers (``id`` attribute) should be avoided. In generic applications
   and modules, ``id`` limits the re-usability of components and tends to make
@@ -668,7 +661,6 @@ in order to make the web client slightly lighter.  In that case, we can use the
 With this, the *Counter* widget will load the xmlDependencies files in its
 *willStart* method, so the template will be ready when the rendering is performed.
 
-
 Event system
 ============
 
@@ -760,9 +752,8 @@ The previous example can be updated to use the custom event system:
 
     ... this.trigger_up('valuechange', {value: someValue});
 
-
 Registries
-===========
+==========
 
 A common need in the Odoo ecosystem is to extend/change the behaviour of the
 base system from the outside (by installing an application, i.e. a different
@@ -799,7 +790,6 @@ action registry
   action.  In version 11, each value should simply be a subclass of *Widget*.
   However, in version 12, the values are required to be *AbstractAction*.
 
-
 Communication between widgets
 =============================
 
@@ -867,7 +857,6 @@ Cross component
           },
       });
 
-
     In this example, we use the bus exported by *web.core*, but this is not
     required. A bus could be created for a specific purpose.
 
@@ -884,7 +873,7 @@ events, these events bubble up to a service provider, which will ask a service
 to perform a task, then maybe return an answer.
 
 Service
---------
+-------
 
 A service is an instance of the *AbstractService* class.  It basically only has
 a name and a few methods.  Its job is to perform some work, typically something
@@ -916,7 +905,6 @@ dispatch the custom events.  In the *backend* (web client), this is done by the
 main web client instance. Note that the code for the service provider comes from
 the *ServiceProviderMixin*.
 
-
 Widget
 ------
 
@@ -975,7 +963,7 @@ may need to directly call a controller (available on some route).
     });
 
 Notifications
-==============
+=============
 
 The Odoo framework has a standard way to communicate various information to the
 user: notifications, which are displayed on the top right of the user interface.
@@ -1010,9 +998,9 @@ The notification system in Odoo is designed with the following components:
 
 - an helper function in *ServiceMixin*: *displayNotification*
 
-
 Displaying a notification
 -------------------------
+
 The most common way to display a notification is by using the method that come
 from the *ServiceMixin*:
 
@@ -1098,7 +1086,6 @@ the class variable SystrayMenu.items.
 
     SystrayMenu.Items.push(MySystrayWidget);
 
-
 Ordering
 --------
 
@@ -1112,7 +1099,6 @@ left).
 
     MySystrayWidget.prototype.sequence = 100;
 
-
 Translation management
 ======================
 
@@ -1207,7 +1193,7 @@ client for everyone), and for data which is required early in the initialization
 process.
 
 Views
-======
+=====
 
 The word 'view' has more than one meaning. This section is about the design of
 the javascript code of the views, not the structure of the *arch* or anything
@@ -1216,7 +1202,6 @@ else.
 In 2017, Odoo replaced the previous view code with a new architecture.  The
 main need was to separate the rendering logic from the model logic.
 
-
 Views (in a generic sense) are now described with  4 pieces: a View, a
 Controller, a Renderer and a Model.  The API of these 4 pieces is described in
 the AbstractView, AbstractController, AbstractRenderer and AbstractModel classes.
@@ -2090,6 +2075,7 @@ reference (FieldReference)
 
 Widgets
 -------
+
 week_days (WeekDays)
   This field displays a list of checkboxes for week days, 1 checkbox for each day
   and allow the user to select a subset of the choices.
@@ -2162,7 +2148,6 @@ Registering the client action:
           <field name="tag">my-custom-action</field>
       </record>
 
-
 Using the control panel
 -----------------------
 

content/developer/reference/frontend/mobile.rst

@@ -1,9 +1,8 @@
-
 .. _reference/mobile:
 
-==================
+=================
 Mobile JavaScript
-==================
+=================
 
 Introduction
 ============
@@ -11,15 +10,16 @@ Introduction
 In Odoo 10.0 we released a mobile app which allows you to access all **Odoo apps**
 (even your customized modules).
 
-The application is a combination of **Odoo Web** and **Native Mobile
-components**. In other words it is a Odoo Web instance loaded inside a native, mobile, WebView container.
+The application is a combination of **Odoo Web** and **Native Mobile components**. In other words it
+is a Odoo Web instance loaded inside a native, mobile, WebView container.
 
 This page documents how you can access mobile native components like Camera,
 Vibration, Notification and Toast through Odoo Web (via JavaScript). For this, you
 do not need to be a mobile developer, if you know Odoo JavaScript API you can
 access all available mobile features.
 
-.. warning:: These features work with **Odoo Enterprise 10.0+** only
+.. warning::
+   These features work with **Odoo Enterprise 10.0+** only
 
 How does it work?
 =================
@@ -64,7 +64,7 @@ Methods
    a data JSON dictionary
 
 Show Toast in device
-.....................
+~~~~~~~~~~~~~~~~~~~~
 
 .. js:function:: showToast
 
@@ -80,10 +80,8 @@ remains visible and interactive.
 
 .. image:: mobile/toast.png
 
-
 Vibrating device
-................
-
+~~~~~~~~~~~~~~~~
 
 .. js:function:: vibrate
 
@@ -97,7 +95,7 @@ Vibrate mobile device with given duration.
     mobile.methods.vibrate({'duration': 100});
 
 Show snackbar with action
-.........................
+~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. js:function:: showSnackBar
 
@@ -122,7 +120,7 @@ displayed at a time.
 .. image:: mobile/snackbar.png
 
 Showing notification
-.....................
+~~~~~~~~~~~~~~~~~~~~
 
 .. js:function:: showNotification
 
@@ -143,7 +141,7 @@ view at any time.
 
 
 Create contact in device
-.........................
+~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. js:function:: addContact
 
@@ -176,7 +174,7 @@ Create a new device contact with the given contact details.
 .. image:: mobile/mobile_contact_create.png
 
 Scanning barcodes
-..................
+~~~~~~~~~~~~~~~~~
 
 .. js:function:: scanBarcode
 
@@ -198,7 +196,7 @@ The barcode API can read the following barcode formats:
     });
 
 Switching account in device
-...........................
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. js:function:: switchAccount
 

content/developer/reference/frontend/owl_components.rst

@@ -489,7 +489,7 @@ open themselves on mouse hover, without the need for a click.
 
 
 Example: Direct Siblings Dropdown
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 When one dropdown toggler is clicked (**File** , **Edit** or **About**), the
 others will open themselves on hover.

content/developer/reference/frontend/qweb.rst

@@ -257,9 +257,8 @@ exists in 3 different forms:
 setting variables
 =================
 
-QWeb allows creating variables from within the template, to memoize a
-computation (to use it multiple times), give a piece of data a clearer name,
-...
+QWeb allows creating variables from within the template, to memoize a computation (to use it
+multiple times), give a piece of data a clearer name, ...
 
 This is done via the ``set`` directive, which takes the name of the variable
 to create. The value to set can be provided in two ways:
@@ -374,7 +373,7 @@ templates:
   will not strip that information from safe content.
 
 Creating safe content using :class:`~markupsafe.Markup`
-'''''''''''''''''''''''''''''''''''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 See the official documentation for explanations, but the big advantage of
 :class:`~markupsafe.Markup` is that it's a very rich type overrinding
@@ -471,12 +470,12 @@ Exclusive directives
 --------------------
 
 Asset bundles
-'''''''''''''
+~~~~~~~~~~~~~
 
 .. todo:: have fme write these up because I've no idea how they work
 
 "smart records" fields formatting
-'''''''''''''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The ``t-field`` directive can only be used when performing field access
 (``a.b``) on a "smart" record (result of the ``browse`` method). It is able
@@ -511,7 +510,7 @@ are also done only once.
 The content can only use the root values.
 
 Why and when to use ``t-cache``?
-''''''''''''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 This directive is used to speed up the rendering, by caching parts of the final
 document, which may save queries to the database.  However, it should be used
@@ -542,7 +541,7 @@ the template, the rendering of what comes after it could be different than if
 there was no ``t-cache`` directive.
 
 What if there is a ``t-cache`` inside a ``t-cache``?
-''''''''''''''''''''''''''''''''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The parts are cached. Each containing only the string corresponding to its
 rendering. Thus, the ``t-cache`` inside will probably be read less often, its
@@ -550,7 +549,7 @@ cache key will not necessarily be used. If this must be the case, then you may
 need to add a ``t-nocache`` (on the same node or a parent).
 
 What is ``t-nocache`` used for?
-'''''''''''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 If you want to cache part of a template with ``t-cache`` but a small piece must
 remain dynamic and be evaluated at cache times. However, the part in
@@ -562,7 +561,7 @@ investigate). However, in the menu, we want the ecommerce cart to be always up
 to date. So there is a ``t-nocache`` to keep this part dynamic.
 
 The base of ``t-cache``
-'''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~~
 
 The ``t-cache`` directive allows you to store the rendered result of a template.
 The **key expression** (eg 42: ``t-cache="42"``) will be evaluated as a python
@@ -587,7 +586,7 @@ condition. And if a module modifies the record, the write_date being modified,
 the cached value is discarded.
 
 ``t-cache`` and scoped values (``t-set``, ``t-foreach``...)
-'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Values in ``t-cache`` are scoped, this involves a change in behavior between
 having or not having ``t-cache`` on one of the parent nodes. Don't forget to
@@ -626,7 +625,7 @@ Will render::
 
 
 The base of ``t-nocache``
-'''''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The template part contained in a node with a ``t-nocache`` attribute is not
 cached. This content is therefore **dynamic** and is rendered systematically.
@@ -655,7 +654,7 @@ Here the ``<i>`` tag that contains the container will always be rendered. While
 the rest is as a single string in the cache.
 
 ``t-nocache`` and scoped root values (``t-set``, ``t-foreach``...)
-''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The contents of the ``t-nocache`` tag can be used for documentation and to
 explain why the directive is added.
@@ -697,7 +696,7 @@ the rest is as a single string in the cache. The counter is not updated by the
 ``t-set`` out of the ``t-nocache``
 
 ``t-nocache-*`` add some primitive values in the cache
-'''''''''''''''''''''''''''''''''''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 In order to be able to use values generated in the template, it is possible to
 cache them. The directive is used as ``t-nocache-*="expr"`` where ``*`` is the
@@ -725,7 +724,7 @@ Helpers
 -------
 
 Request-based
-'''''''''''''
+~~~~~~~~~~~~~
 
 Most Python-side uses of QWeb are in controllers (and during HTTP requests),
 in which case templates stored in the database (as
@@ -742,7 +741,7 @@ This automatically creates a :class:`~odoo.http.Response` object which can
 be returned from the controller (or further customized to suit).
 
 View-based
-''''''''''
+~~~~~~~~~~
 
 At a deeper level than the previous helper is the ``_render`` method on
 ``ir.qweb`` (use the datable) and the public module method ``render``
@@ -808,7 +807,7 @@ Exclusive directives
 --------------------
 
 Defining templates
-''''''''''''''''''
+~~~~~~~~~~~~~~~~~~
 
 The ``t-name`` directive can only be placed at the top-level of a template
 file (direct children to the document root)::
@@ -829,7 +828,7 @@ names to indicate hierarchical relationships.
 .. _reference/qweb/template_inheritance:
 
 Template inheritance
-''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~
 
 Template inheritance is used to either:
  - Alter existing templates in-place, e.g. to add information to templates
@@ -866,7 +865,7 @@ Extension inheritance (in-place transformation)::
     </t>
 
 Old inheritance mechanism (deprecated)
-''''''''''''''''''''''''''''''''''''''
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Template inheritance is performed via the ``t-extend`` directive which takes
 the name of the template to alter as parameter.

content/developer/reference/frontend/services.rst

@@ -673,8 +673,7 @@ When a rpc fails, then:
 
 * the promise representing the rpc is rejected, so the calling code will crash,
   unless it handles the situation
-*
-  an event ``RPC_ERROR`` is triggered on the main application bus. The event payload
+* an event ``RPC_ERROR`` is triggered on the main application bus. The event payload
   contains a description of the cause of the error:
 
   If it is a server error (the server code threw an exception). In that case

content/developer/reference/standard_modules/account/account_report.rst

@@ -1,7 +1,6 @@
-
-===============
+======
 Report
-===============
+======
 
 .. automodel:: odoo.addons.account.models.account_report.AccountReport
     :main:

content/developer/reference/standard_modules/account/account_report_line.rst

@@ -1,7 +1,6 @@
-
-===============
+===========
 Report Line
-===============
+===========
 
 .. automodel:: odoo.addons.account.models.account_report.AccountReportLine
     :main: