From 06f328a39eb513b32c9a8446b941716ca9979465 Mon Sep 17 00:00:00 2001 From: Victor Feyens Date: Thu, 17 Nov 2022 15:54:48 +0000 Subject: [PATCH] [FIX] *: unbalanced literal markups Part-of: odoo/documentation#2978 --- content/applications/websites/website/optimize/seo.rst | 2 +- content/developer/howtos/rdtraining/K_dashboard.rst | 6 +++--- content/developer/reference/javascript/qweb.rst | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/content/applications/websites/website/optimize/seo.rst b/content/applications/websites/website/optimize/seo.rst index 2251c7989..4151d7102 100644 --- a/content/applications/websites/website/optimize/seo.rst +++ b/content/applications/websites/website/optimize/seo.rst @@ -621,7 +621,7 @@ robots.txt ---------- When indexing your website, search engines take a first look at the -general indexing rules of the a``/robots.txt`` file (allowed robots, +general indexing rules of the ``/robots.txt`` file (allowed robots, sitemap path, etc.). Odoo automatically creates it. Its content is: User-agent: \* diff --git a/content/developer/howtos/rdtraining/K_dashboard.rst b/content/developer/howtos/rdtraining/K_dashboard.rst index 6eebcc341..8b77dcfd8 100644 --- a/content/developer/howtos/rdtraining/K_dashboard.rst +++ b/content/developer/howtos/rdtraining/K_dashboard.rst @@ -36,7 +36,7 @@ File Structure You probably have already guessed that since dashboard views are an Enterprise view, they must have a dependency on an Enterprise module. The Enterprise module is ``web_dashboard``. Don't forget to add it to your manifest file! It is standard to add dashboards intended to be used as a -``view_mode`` for one of your module's models (in the ``model`` folder``) to the views directory +``view_mode`` for one of your module's models (in the ``model`` folder) to the views directory (i.e. the same file that contains the other views for the same model). It is standard to create a separate Enterprise module to add extra Enterprise views and features to @@ -319,8 +319,8 @@ View Now that we have our model, we can make its dashboard view. There is no difference to how its made except that its file is located in the ``report`` folder. Since it is a new model not linked to any other model, we will also have to add a new menuitem to view our dashboard. Typically SQL views -are added under a first level menu called ``Reporting` (because it's a report, surprise!). Do you -remember how to add a ``menuitem``? If not, revisit :ref:`howto/rdtraining/06_firstui`) again. +are added under a first level menu called ``Reporting`` (because it's a report, surprise!). Do you +remember how to add a ``menuitem``? If not, revisit :ref:`howto/rdtraining/06_firstui` again. .. exercise:: Create report view. diff --git a/content/developer/reference/javascript/qweb.rst b/content/developer/reference/javascript/qweb.rst index f5a4bafc7..43d32d0ee 100644 --- a/content/developer/reference/javascript/qweb.rst +++ b/content/developer/reference/javascript/qweb.rst @@ -173,7 +173,7 @@ variables for various data points: index These extra variables provided and all new variables created into the -``foreach`` are only available in the scope of the``foreach``. If the +``foreach`` are only available in the scope of the ``foreach``. If the variable exists outside the context of the ``foreach``, the value is copied at the end of the foreach into the global context.