[FIX] discuss: broken link in ice_servers.rst

The deploy documentation is assuming that `/etc/odoo.conf` is the
default config file, which is not the case.

With this commit, the configuration file references the cli
documentation.

closes odoo/documentation#4802

X-original-commit: 8aed7988ba
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Christophe Monniez (moc) <moc@odoo.com>

conf.py

@@ -193,7 +193,7 @@ todo_include_todos = False
 
 intersphinx_mapping = {
     'python': ('https://docs.python.org/3/', None),
-    'werkzeug': ('https://werkzeug.palletsprojects.com/en/1.0.x/', None),
+    'werkzeug': ('https://werkzeug.palletsprojects.com/en/2.3.x/', None),
 }
 
 github_user = 'odoo'

content/administration/install/deploy.rst

@@ -43,7 +43,7 @@ Configuration samples
 
 * Show only databases with names beginning with 'mycompany'
 
-in ``/etc/odoo.conf`` set:
+in :ref:`the configuration file <reference/cmdline/config_file>` set:
 
 .. code-block:: ini
 
@@ -55,7 +55,7 @@ in ``/etc/odoo.conf`` set:
   was sent to ``www.mycompany.com`` or ``mycompany.co.uk``, but not
   for ``www2.mycompany.com`` or ``helpdesk.mycompany.com``.
 
-in ``/etc/odoo.conf`` set:
+in :ref:`the configuration file <reference/cmdline/config_file>` set:
 
 .. code-block:: ini
 
@@ -150,7 +150,7 @@ Configuration sample
 * with 'pwd' as a password
 * filtering only db with a name beginning with 'mycompany'
 
-in ``/etc/odoo.conf`` set:
+in :ref:`the configuration file <reference/cmdline/config_file>` set:
 
 .. code-block:: ini
 
@@ -238,7 +238,7 @@ Configuration sample
 * We'll use 8 workers + 1 for cron. We'll also use a monitoring system to measure cpu load, and check if it's between 7 and 7.5 .
 * RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo
 
-in ``/etc/odoo.conf``:
+in :ref:`the configuration file <reference/cmdline/config_file>`:
 
 .. code-block:: ini
 
@@ -273,7 +273,7 @@ Configuration sample
 * Redirect http requests to https
 * Proxy requests to odoo
 
-in ``/etc/odoo.conf`` set:
+in :ref:`the configuration file <reference/cmdline/config_file>` set:
 
 .. code-block:: ini
 

content/administration/maintain/enterprise.rst

@@ -1,9 +1,9 @@
 
 .. _setup/enterprise:
 
-===============================
-Upgrade Community to Enterprise
-===============================
+===================================
+Switch from Community to Enterprise
+===================================
 
 Depending on your current installation, there are multiple ways to upgrade
 your community version.
@@ -98,7 +98,7 @@ On Windows
 
   .. code-block:: console
 
-    $ odoo.exe -d <database_name> -i web_enterprise --stop-after-init
+    $ ..\python\python.exe odoo-bin -d <database_name> -i web_enterprise --stop-after-init
 
 * No need to manually launch the server, the service is running.
   You should be able to connect to your Odoo Enterprise instance using your usual

content/administration/odoo_sh/getting_started/settings.rst

@@ -45,41 +45,101 @@ these databases if they have one, using their regular credentials.
 
 In addition, they cannot use the webshell nor have access to the server logs.
 
-+---------------------+-----------------+-----------+-----------+
-|                     |                 | User      | Admin     |
-+=====================+=================+===========+===========+
-|Development          | History         |     X     |     X     |
-+---------------------+-----------------+-----------+-----------+
-|                     | 1-click connect |     X     |     X     |
-+---------------------+-----------------+-----------+-----------+
-|                     | Logs            |     X     |     X     |
-+---------------------+-----------------+-----------+-----------+
-|                     | Shell/SSH       |     X     |     X     |
-+---------------------+-----------------+-----------+-----------+
-|                     | Mails           |     X     |     X     |
-+---------------------+-----------------+-----------+-----------+
-|                     | Settings        |     X     |     X     |
-+---------------------+-----------------+-----------+-----------+
-|Production & Staging | History         |     X     |     X     |
-+---------------------+-----------------+-----------+-----------+
-|                     | 1-click connect |           |     X     |
-+---------------------+-----------------+-----------+-----------+
-|                     | Logs            |           |     X     |
-+---------------------+-----------------+-----------+-----------+
-|                     | Shell/SSH       |           |     X     |
-+---------------------+-----------------+-----------+-----------+
-|                     | Mails           |           |     X     |
-+---------------------+-----------------+-----------+-----------+
-|                     | Monitoring      |           |     X     |
-+---------------------+-----------------+-----------+-----------+
-|                     | Backups         |           |     X     |
-+---------------------+-----------------+-----------+-----------+
-|                     | Settings        |     X     |     X     |
-+---------------------+-----------------+-----------+-----------+
-|Status               |                 |     X     |     X     |
-+---------------------+-----------------+-----------+-----------+
-|Settings             |                 |           |     X     |
-+---------------------+-----------------+-----------+-----------+
+.. list-table::
+   :header-rows: 1
+   :widths: auto
+
+   * -
+     -
+     - User
+     - Admin
+   * - Development
+     - History
+     - |green|
+     - |green|
+   * -
+     - 1-click connect
+     - |green|
+     - |green|
+   * -
+     - Logs
+     - |green|
+     - |green|
+   * -
+     - Shell/SSH
+     - |green|
+     - |green|
+   * -
+     - Mails
+     - |green|
+     - |green|
+   * -
+     - Upgrade
+     - |green|
+     - |green|
+   * -
+     - Settings
+     - |green|
+     - |green|
+   * - Production & Staging
+     - History
+     - |green|
+     - |green|
+   * -
+     - 1-click connect
+     -
+     - |green|
+   * -
+     - Logs
+     -
+     - |green|
+   * -
+     - Shell/SSH
+     -
+     - |green|
+   * -
+     - Mails
+     -
+     - |green|
+   * -
+     - Monitoring
+     -
+     - |green|
+   * -
+     - Backups
+     -
+     - |green|
+   * -
+     - Upgrade
+     -
+     - |green|
+   * -
+     - Settings
+     - |green|\*
+     - |green|
+   * - Status
+     -
+     - |green|
+     - |green|
+   * - Settings
+     -
+     -
+     - |green|
+
+.. note::
+    \* Only in staging branches
+
+.. |green| raw:: html
+
+   <span class="text-success" style="font-size: 32px; line-height: 0.5">●</span>
+
+.. |orange| raw:: html
+
+   <span class="text-warning" style="font-size: 32px; line-height: 0.5">●</span>
+
+.. |red| raw:: html
+
+   <span class="text-danger" style="font-size: 32px; line-height: 0.5">●</span>
 
 Public Access
 =============

content/applications/finance/accounting/payments/follow_up.rst

@@ -4,8 +4,8 @@ Follow-up on invoices
 
 A follow-up message can be sent to customers when a payment is overdue. Odoo helps you identify late
 payments and allows you to schedule and send the appropriate reminders using **follow-up actions**
-that trigger automatically one or more actions according to the number of overdue days. You can send
-your follow-ups via different means such as email, post, or SMS.
+that automatically trigger one or more actions according to the number of overdue days. You can send
+your follow-ups via different means, such as email, post, or SMS.
 
 .. seealso::
    - `Odoo Tutorials: Payment Follow-up <https://www.odoo.com/slides/slide/payment-follow-up-1682>`_
@@ -48,7 +48,7 @@ options:
    - **%(company_name)s**: User's company name.
 
 .. tip::
-   To send a reminder before the actual due date is reached, set a negative number of due days.
+   Set a negative number of days to send a reminder before the actual due date.
 
 Follow-up reports
 =================
@@ -66,16 +66,15 @@ It is up to you to decide how to remind your customer. You can select :guilabel:
 :guilabel:`Done` to view the next follow-up that needs your attention.
 
 .. note::
-   - The contact information available on the invoice or on the contact form is used to send the
-     reminder.
+   - The contact information on the invoice or the contact form is used to send the reminder.
    - When the reminder is sent, it is documented in the chatter of the invoice.
    - If it is not the right time for a reminder, you can specify the :guilabel:`Next Reminder Date`
      and click on :guilabel:`Remind me later`. You will get the next report according to the next
      reminder date set on the statement.
 
 .. tip::
-   Reconcile your bank statements right before launching your follow-up process to avoid sending a
-   reminder to a customer that has already paid you.
+   Reconcile all bank statements right before launching the follow-up process to avoid sending a
+   reminder to a customer that has already paid.
 
 Debtor's trust level
 --------------------

content/applications/finance/accounting/taxes/eu_distance_selling.rst

@@ -2,68 +2,64 @@
 EU intra-community distance selling
 ===================================
 
-**Distance sales within the European Union** include cross-border sales of goods and services to a
-private consumer (B2C) in another EU Member State when the seller doesn't meet face-to-face with the
-customer. Organizations must ensure that the VAT on distance sales is paid to the Member State in
-which the goods or services are delivered.
+EU intra-community distance selling involves the cross-border trade of goods and services from
+vendors registered for VAT purposes to individuals (B2C) located in a European Union member state.
+The transaction is conducted remotely, typically through online platforms, mail orders, telephone,
+or other means of communication.
+
+EU intra-community distance selling is subject to specific VAT rules and regulations. The vendor
+must charge VAT per the VAT rate applicable in the buyer's country.
 
 .. note::
-   This remains true even if your organization is located outside of the European Union.
-
-While this regulation mainly applies to :doc:`eCommerce <../../../websites/ecommerce>` sales to
-private EU consumers, it is also valid for mail order sales and telesales.
-
-The Union **One-Stop Shop (OSS)** is an online portal where businesses can register for the OSS and
-declare their intra-community distance sales. Each EU member state integrates an online OSS portal.
-
-The **EU intra-community Distance Selling** feature helps your organization comply with this
-regulation by creating and configuring new :doc:`fiscal positions <fiscal_positions>` and
-:doc:`taxes <../taxes>` based on your company's country.
-
-.. seealso::
-   - `European Commission: OSS | Taxation and Customs Union
-     <https://ec.europa.eu/taxation_customs/business/vat/oss_en>`_
-
-.. _eu_distance_selling/configuration:
+   This remains applicable even if the vendor is located outside of the European Union.
 
 Configuration
 =============
 
-Go to :menuselection:`Accounting/Invoicing --> Settings --> Taxes`, then enable **EU intra-community
-Distance Selling** (or **EU Digital Goods VAT** if you created your database before July 1, 2021),
-and *Save*.
+The **EU Intra-community Distance Selling** feature helps you comply with this regulation by
+creating and configuring new **fiscal positions** and **taxes** based on your company's country. To
+enable it, go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes`, tick
+:guilabel:`EU Intra-community Distance Selling`, and :guilabel:`Save`.
 
 .. image:: eu_distance_selling/enable-feature.png
-   :align: center
    :alt: EU intra-community Distance Selling feature in Odoo Accounting settings
 
-.. important::
-   Please :ref:`upgrade the module <general/upgrade>` `l10n_eu_service` if you already installed it
-   before **July 1, 2021**, or if you activated the feature **EU Digital Goods VAT** in the
-   Accounting settings. Then, make sure to :ref:`refresh the tax mapping
-   <eu_distance_selling/refresh-mapping>`.
+.. tip::
+   Whenever you add or modify taxes, you can automatically update your fiscal positions. To do so,
+   go to :menuselection:`Accounting/Invoicing --> Settings --> Taxes --> EU Intra-community Distance
+   Selling` and click on the :guilabel:`Refresh tax mapping`.
 
-.. _eu_distance_selling/taxes:
-
-Fiscal Positions and Taxes
-==========================
-
-Once enabled, the feature automatically creates all the necessary taxes and fiscal positions needed
-for each EU member state, based on your company's country.
-
-We highly recommend checking that the proposed mapping is suitable for the products and services you
-sell before using it.
-
-.. _eu_distance_selling/refresh-mapping:
-
-Refresh tax mapping
--------------------
-
-Whenever you add or modify taxes, you can update automatically your fiscal positions.
-
-To do so, go to :menuselection:`Accounting/Invoicing --> Settings --> Taxes --> EU intra-community
-Distance Selling` and click on the *Refresh tax mapping* button.
+.. note::
+   We highly recommend checking that the proposed mapping is suitable for the products and services
+   you sell before using it.
 
 .. seealso::
-   - :doc:`fiscal_positions`
    - :doc:`../taxes`
+   - :doc:`../../fiscal_localizations`
+   - :doc:`fiscal_positions`
+
+One-Stop Shop (OSS)
+===================
+
+The :abbr:`OSS (One-Stop Shop)` system introduced by the European Union simplifies VAT collection
+for **cross-border** sales of goods and services. It primarily applies to business-to-consumer
+**(B2C)** cases. With the OSS, businesses can register for VAT in their home country and use a
+single online portal to handle VAT obligations for their sales within the EU. There are **two
+primary schemes**: the **Union OSS** scheme for cross-border services and the **Import OSS** scheme
+for goods valued at or below €150.
+
+Reports
+-------
+
+To generate **OSS sales** or **OSS imports** reports and submit them onto the OSS portal, go to
+:menuselection:`Accounting --> Reporting --> Tax Report`, click :guilabel:`Tax Report: Global
+Summary`, and select either :guilabel:`OSS Sales` or :guilabel:`OSS Imports`. Once selected, click
+on :guilabel:`PDF`, :guilabel:`XLSX`, or :guilabel:`XML` in the top-left corner. This generates the
+currently-opened report in the selected format. Once generated, log into the platform of your
+competent federal authority to submit it onto the OSS portal.
+
+.. image:: eu_distance_selling/oss-report.png
+   :alt: OSS reports view
+
+.. seealso::
+   - `European Commission: OSS | Taxation and Customs Union <https://ec.europa.eu/taxation_customs/business/vat/oss_en>`_

content/applications/finance/expenses.rst

@@ -4,231 +4,533 @@
 Expenses
 ========
 
-**Odoo Expenses** streamlines the management of expenses. Employees can submit their expenses;
-managers can approve them; accountants can record them and process the payments.
+Odoo **Expenses** streamlines the management of expenses.  After an employee submits their expenses
+in Odoo, the expenses are reviewed by management and accounting teams. Once approved, payments can
+then be processed and disbursed back to the employee for reimbursement(s).
 
 .. seealso::
-   - `Odoo Expenses: product page <https://www.odoo.com/app/expenses>`_
+   `Odoo Expenses: product page <https://www.odoo.com/app/expenses>`_
 
-How to set expense types
-========================
+Set expense types
+=================
 
-The first step to track expenses is to configure the expense types (managed as products in Odoo)
-that your company allows, from the *Configuration* menu.
-When a specific expense is reimbursed at a fixed price, set a cost on the product.
-Otherwise keep the cost at 0.0 and employees will report the real cost per expense.
+The first step to track expenses is to configure the different *expense types* for the company
+(managed as *products* in Odoo). Each "product" can be as specific or generalized as needed. Go to
+:menuselection:`Expenses app --> Configuration --> Expense Products` to view the current expensable
+products in a default kanban view.
 
-.. image:: expenses/product.png
+.. image:: expenses/products.png
    :align: center
+   :alt: Set expense costs on products.
 
-Here are some examples:
-
-* Restaurant:
-
-  * Cost: 0.00 (the cost of the ticket will be recorded on every expense)
-* Travel with Personal Car:
-
-  * Cost: 0.30 (the price per mile reimbursed by the company is fixed)
-* Hotel:
-
-  * Cost: 0.00 (the cost of the ticket will be recorded on every expense)
-
-* Others:
-
-  * Cost: 0.0
-
-Don't forget to set an expense tax on each expense type
-(and an account if you use Odoo Accounting).
-It's usually a good practice to use a tax that is configured
-with :ref:`Tax Included in Price <taxes/included-in-price>`.
-That way, employees report expenses with
-prices including taxes, which is usually the expected behaviour.
+To create a new expense product, click :guilabel:`Create`. A product form will appear. Only two
+fields are required, the :guilabel:`Product Name` and the :guilabel:`Unit of Measure`. Enter the
+:guilabel:`Product Name` in the field, and select the :guilabel:`Unit of Measure` from the drop-down
+menu (most products will be set to :guilabel:`Units`).
 
 .. tip::
-    The *Sales* app allows you to specify units of measure for your
-    expense types (units, miles, nights, etc.).
-    Go to :menuselection:`Sales --> Configuration --> Settings` and check
-    *Some products may be sold/purchased in different units of measure (advanced)*.
+   The *Sales* app is where specification on the units of measure are created and edited (e.g.
+   units, miles, nights, etc.). Go to :menuselection:`Sales app --> Configuration --> Settings` and
+   ensure `Units of Measure` is checked off in the `Product Catalog` section. Click on the
+   :guilabel:`Units of Measure` internal link to view, create, and edit the units of measure. Refer
+   to :doc:`this document </applications/inventory_and_mrp/inventory/management/products/uom>` to
+   learn more about units of measure and how to configure them.
 
-
-How to record expenses
-======================
-
-Manually
---------
-
-As an employee (Employee in user access rights), you can record
-expenses from :menuselection:`My Expenses --> Expenses to Submit`.
-
-.. image:: expenses/submit_01.png
+.. image:: expenses/new-expense-product.png
    :align: center
+   :alt: Set expense costs on products.
 
-1. Select the related product and enter either the total amount
-   you paid (with Quantity = 1) or the unit price if Quantity is
-   countable (e.g. number of hotel nights).
-2. Enter the expense date.
-3. Choose if you paid the bill on your own (and expect to be reimbursed)
-   or if the company paid directly (e.g. if you used a company's credit card).
-4. Set the bill reference, add some notes if requested and attach a
-   photo/scan of the receipt from the discussion thread.
-   That will help the manager and the accountant validate it.
+The :guilabel:`Cost` field on the product form is populated with a value of `0.00` by default. When
+a specific expense should always be reimbursed for a particular price, enter that amount in the
+:guilabel:`Cost` field. Otherwise, leave the :guilabel:`Cost` set to `0.00`, and employees will
+report the actual cost when submitting an expense report.
 
-.. image:: expenses/submit_02.png
+.. example::
+   Here are some examples for when to set a specific :guilabel:`Cost` on a product vs. leaving the
+   :guilabel:`Cost` at `0.00`:
+
+   - **Meals**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an expense for a meal, they
+     enter the actual amount of the bill and will be reimbursed for that amount. An expense for a
+     meal costing $95.23 would equal a reimbursement for $95.23.
+   - **Mileage**: Set the :guilabel:`Cost` to `0.30`. When an employee logs an expense for
+     "mileage", they enter the number of miles driven, and are reimbursed 0.30 per mile they
+     entered. An expense for 100 miles would equal a reimbursement for $30.00.
+   - **Monthly Parking**: Set the :guilabel:`Cost` to `75.00`. When an employee logs an expense for
+     "monthly parking", the reimbursement would be for $75.00.
+   - **Expenses**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an expense that is not
+     a meal, mileage, or monthly parking, they use the generic :guilabel:`Expenses` product. An
+     expense for a laptop costing $350.00 would be logged as an :guilabel:`Expenses` product, and
+     the reimbursement would be for $350.00.
+
+Select an :guilabel:`Expense Account` if using the Odoo *Accounting* app. It is recommended to check
+with the accounting department to determine the correct account to reference in this field as it
+will affect reports.
+
+Set a tax on each product in the :guilabel:`Vendor Taxes` and :guilabel:`Customer Taxes` fields if
+applicable. It is considered good practice to use a tax that is configured with :ref:`Tax Included
+in Price <taxes/included-in-price>`. Taxes will be automatically configured if this is set.
+
+.. _expenses/new:
+
+Record expenses
+===============
+
+Manually create a new expense
+-----------------------------
+
+To record a new expense, begin in the main :menuselection:`Expenses` app dashboard, which presents
+the default :guilabel:`My Expenses to Report` view. This view can also be accessed from
+:menuselection:`Expenses app --> My Expenses --> My Expenses to Report`.
+
+First, click :guilabel:`Create`, and then fill out the various fields on the form.
+
+- :guilabel:`Description`: Enter a short description for the expense in the :guilabel:`Description`
+  field. This should be short and informative, such as `lunch with client` or `hotel for
+  conference`.
+- :guilabel:`Product`: Select the product from the drop-down menu that most closely corresponds to
+  the expense. For example, an airplane ticket would be appropriate for an expense
+  :guilabel:`Product` named :guilabel:`Air Travel`.
+- :guilabel:`Unit Price`: Enter the total amount paid for the expense in one of two ways:
+
+  #. If the expense is for one single item/expense, enter the cost in the :guilabel:`Unit Price`
+     field, and leave the :guilabel:`Quantity` `1.00`.
+  #. If the expense is for multiples of the same item/expense, enter the price *per unit* in the
+     :guilabel:`Unit Price` field, and enter the *quantity of units* in the :guilabel:`Quantity`
+     field.
+
+     .. example::
+        In the case of a hotel stay, for example, the :guilabel:`Unit Price` would be set as the
+        cost *per night*, and set the :guilabel:`Quantity` to the *number of nights* stayed.
+
+- :guilabel:`Taxes`: If taxes were paid on the expense, select the tax percentage using the
+  drop-down menu. Tax options are pre-configured based on the localization setting selected when the
+  database was created. Adding any new taxes should only be done when necessary.
+
+  .. note::
+     When a tax is selected, the :guilabel:`Total` value will update in real time to show the added
+     taxes.
+
+- :guilabel:`Paid By`: Click the radio button to indicate who paid for the expense and should be
+  reimbursed. If the employee paid for the expense (and should be reimbursed) select
+  :guilabel:`Employee (to reimburse)`. If the company paid directly instead (e.g. if the company
+  credit card was used to pay for the expense) select :guilabel:`Company`.
+- :guilabel:`Expense Date`: Using the calendar module, enter the date the expense was incurred. Use
+  the :guilabel:`< (left)` and :guilabel:`> (right)` arrows to navigate to the correct month, then
+  click on the specific day to enter the selection.
+- :guilabel:`Bill Reference`: If there is any reference text that should be included for the
+  expense, enter it in this field.
+- :guilabel:`Account`: Select the expense account that this expense should be logged on from the
+  drop-down menu.
+- :guilabel:`Employee`: Using the drop-down menu, select the employee this expense is for.
+- :guilabel:`Customer to Reinvoice`: If the expense is something that should be paid for by a
+  customer, select the customer that will be invoiced for this expense from the drop-down menu. For
+  example, if a customer wishes to have an on-site meeting, and agrees to pay for the expenses
+  associated with it (such as travel, hotel, meals, etc.), then all expenses tied to that meeting
+  would indicate that customer as the :guilabel:`Customer to Reinvoice`.
+- :guilabel:`Analytic Account`: Select the account the expense should be written against from the
+  drop-down menu.
+- :guilabel:`Company`: If multiple companies are set-up, select the company this expense should be
+  filed for from the drop-down menu. If there is only one company, this field will be automatically
+  populated.
+- :guilabel:`Notes...`: If any notes are needed in order to clarify the expense, enter them in the
+  notes field.
+
+Once all the fields have been filled out, click :guilabel:`Save`.
+
+.. image:: expenses/expense-filled-in.png
    :align: center
+   :alt: A filled in expense form for a client lunch.
 
-In one click from emails
-------------------------
+Attach a receipt
+~~~~~~~~~~~~~~~~
 
-Let your employees record their expenses from a simple email.
-Make a snapshot of the receipt and send it by email, or simply forward a bill!
+After the expense is saved, the next step is to attach a receipt. A new :guilabel:`Attach Receipt`
+button appears after the entry is saved, beneath the former :guilabel:`Save` button (which turns
+into an :guilabel:`Edit` button).
 
-The only thing to do is setting up an email alias in
-:menuselection:`Expenses --> Configuration --> Settings` (e.g. *expenses* @mycompany.odoo.com).
-For security purposes, only authenticated employee emails
-(cfr. *Work Email* in employee detail form) are accepted.
-
-.. tip::
-    The expense product is set automatically if the mail subject contains
-    the product's internal reference in first position.
-    Type the expense amount in the mail subject to set it on the expense too (e.g. Ref001 Food 100€).
-
-How to submit expenses to managers
-==================================
-
-When you are ready to submit your expenses to your manager
-(e.g. at the end of a business trip, or once a month),
-go to the menu :menuselection:`My Expenses --> Expenses to Submit`. Select all expenses
-from the list view and click on :menuselection:`Action --> Submit to Manager`.
-Save the newly created expense report (i.e. set of expenses),
-and wait for your manager to approve it.
-
-.. image:: expenses/submit_03.png
+.. image:: expenses/save-receipt.png
    :align: center
+   :alt: Attach a receipt after saving the record.
 
-You can also submit expenses one by one from the *Submit to Manager*
-button on the form view of an expense.
+Click the new :guilabel:`Attach Receipt` button, and a file explorer appears. Navigate to the
+receipt to be attached, and click :guilabel:`Open`. A new :guilabel:`Receipts` smart button appears
+at the top, and the new receipt is recorded in the chatter. More than one receipt can be attached to
+an individual expense, as needed. The number of receipts attached to the expense will be noted on
+the smart button.
 
-All your submitted expense reports can be found in
-:menuselection:`Expenses --> My Expenses --> Expense Reports`.
-
-
-How to approve expenses
-=======================
-
-HR and team managers get an overview of all expense reports to
-validate from the top menu :menuselection:`To Approve --> Expense Reports to Approve`.
-Such users must have at least *Officers* access rights for *Expenses*.
-
-.. image:: expenses/approval_01.png
+.. image:: expenses/receipt-smartbutton.png
    :align: center
+   :alt: Attach a receipt after saving the record.
 
-They can review expense reports, approve or reject them, as well as providing
-feedback thanks to the integrated communication tool.
+Automatically create new expenses from an email
+-----------------------------------------------
 
-.. image:: expenses/approval_02.png
+Instead of individually creating each expense in the *Expenses* app, expenses can be automatically
+created by sending an email to an email alias.
+
+To do so, first, an email alias needs to be configured. Go to :menuselection:`Expenses app -->
+Configuration --> Settings`. Ensure :guilabel:`Incoming Emails` is checked off.
+
+.. image:: expenses/email-alias.png
    :align: center
-
-As a team manager you can easily find the expense reports of your team members.
-You need to be set as manager in the detail form of those employees.
-
-.. image:: expenses/approval_03.png
-   :align: center
-
-
-How to post expenses in accounting
-==================================
-
-Once expense reports approved by managers, the accounting department
-goes to :menuselection:`Expenses --> Accountant --> Expense Reports To Post` to check
-accounts, products and taxes. They can click *Post Journal Entries*
-to post related journal entries into your books.
-To do so, the user must have following access rights:
-
-* Accounting: Accountant or Adviser
-* Expenses: Manager
+   :alt: Create the domain alias by clicking the link.
 
 .. note::
-    To post an expense, a *Home Address* must be set on the employee.
-    If you get a related blocking message when posting, click the employee,
-    go to *Personal Information* tab and select/create the contact of your employee
-    in the address book.
-    A contact has been automatically created if this person is using Odoo.
+   If the domain alias needs to be set up, :guilabel:`Setup your domain alias` will appear beneath
+   the incoming emails check box instead of the email address field. Refer to this documentation for
+   setup instructions and more information: :doc:`/administration/maintain/domain_names`. Once the
+   domain alias is configured, the email address field will be visible beneath the incoming emails
+   section.
 
-How to reimburse employees
-==========================
+Next, enter the email address to be used in the email field, then click :guilabel:`Save`. Now that
+the email address has been entered, emails can be sent to that alias to create new expenses without
+having to be in the Odoo database.
 
-You can now see all the expense reports to reimburse in
-:menuselection:`Expenses --> Accountant --> Expense Reports To Pay`.
-To record the payment or pay by check, click *Register a Payment*.
+To submit an expense via email, create a new email and enter the product's *internal reference* code
+(if available) and the amount of the expense in the email subject. Next, attach the receipt to the
+email. Odoo creates the expense by taking the information in the email subject and combining it with
+the receipt.
 
-See how you can easily manage the payment process in Odoo:
+To check an expense product's internal reference, go to :menuselection:`Expenses app -->
+Configuration --> Expense Products`. If an internal reference is listed on the product, it is
+visible in this view as :guilabel:`(Ref###)`.
 
-* :doc:`accounting/payments/pay_checks`
-* :doc:`accounting/payments/pay_sepa`
+.. image:: expenses/internal-ref-numbers.png
+   :align: center
+   :alt: Internal reference numbers are listed in the main Expense Products view.
 
+To add an internal reference on an expense product, click on the product, then click
+:guilabel:`Edit`. In edit mode, enter the :guilabel:`Internal Reference` in the field. Beneath the
+:guilabel:`Internal Reference` field, this sentence appears: :guilabel:`Use this reference as a
+subject prefix when submitting by email.`.
 
-How to re-invoice expenses to your customers
-============================================
+.. image:: expenses/meals-internal-reference.png
+   :align: center
+   :alt: Internal reference numbers are listed in the main Expense Products view.
 
-If you track expenses on customer projects, you can charge them back to
-your customers automatically.
+.. note::
+   For security purposes, only authenticated employee emails are accepted by Odoo when creating an
+   expense from an email. To confirm an authenticated employee email address, go to the employee
+   card in the :guilabel:`Employees` app, and refer to the :guilabel:`Work Email` in the main field.
+
+   .. image:: expenses/authenticated-email-address.png
+      :align: center
+      :alt: Create the domain alias by clicking the link.
+
+.. example::
+   If submitting an expense via email for a $25.00 meal during a work trip, the email subject would
+   be `Ref005 Meal $25.00`.
+
+   Explanation:
+
+   - The :guilabel:`Internal Reference` for the expense product `Meals` is `Ref005`
+   - The :guilabel:`Cost` for the expense is `$25.00`
+
+Create an expense report
+========================
+
+When expenses are ready to submit (such as at the end of a business trip, or once a month), an
+*expense report* needs to be created. Go to the main :menuselection:`Expenses` app dashboard, which
+displays a default :guilabel:`My Expenses` view, or go to :menuselection:`Expenses app --> My
+Expenses --> My Expenses to Report`.
+
+First, each individual expense for the report must be selected by clicking the check box next to
+each entry, or quickly select all the expenses in the list by clicking the check box next to
+:guilabel:`Expense Date`.
+
+.. image:: expenses/create-report.png
+   :align: center
+   :alt: Select the expenses to submit, then create the report.
+
+Once the expenses have been selected, click the :guilabel:`Create Report` button. The new report
+appears with all the expenses listed, and the number of documents is visible in the
+:guilabel:`Documents` smart button.
+
+It is recommended to add a short summary for each report to help keep expenses organized. Click the
+:guilabel:`Edit` button, and the :guilabel:`Expense Report Summary` field appears. Enter a short
+description for the expense report (such as `Client Trip NYC`, or `Repairs for Company Car`). Next,
+select a :guilabel:`Manager` from the drop-down menu to assign a manager to review the report.
+
+.. image:: expenses/expense-report-summary.png
+   :align: center
+   :alt: Enter a short description and select a manager for the report.
+
+If some expenses are not on the report that should be, they can still be added. Click :guilabel:`Add
+a line` at the bottom of the :guilabel:`Expense` tab. Click the check box next to each expense to
+add, then click :guilabel:`Select`. The items now appear on the report that was just created.
+
+.. image:: expenses/add-an-expense-line.png
+   :align: center
+   :alt: Add more expenses to the report before submitting.
+
+.. note::
+   :guilabel:`Add a line` only appears when the document is in edit mode. It does not appear
+   otherwise.
+
+When all edits have been completed, click :guilabel:`Save`.
+
+Submit an expense report
+------------------------
+
+When an expense report is completed, the next step is to submit the report to a manager for
+approval. Reports must be individually submitted, and cannot be submitted in batches. Open the
+specific report from the list of expense reports (if the report is not already open). To view all
+expense reports, go to :menuselection:`Expenses app --> My Expenses --> My Reports`.
+
+If the list is large, grouping the results by status may be helpful since only reports that are in a
+:guilabel:`Draft` mode need to be submitted, reports with an :guilabel:`Approved` or
+:guilabel:`Submitted` status do not.
+
+.. image:: expenses/expense-status.png
+   :align: center
+   :alt: Submit the report to the manager.
+
+.. note::
+   The status of each report is shown in the :guilabel:`Status` column on the far right. If the
+   :guilabel:`Status` column is not visible, click the :guilabel:`⋮ (additional options)` icon at
+   the end of the row, and check the box next to :guilabel:`Status`.
+
+Click on a report to open it, then click :guilabel:`Submit To Manager`. After submitting a report,
+the next step is to wait for the manager to approve it.
+
+.. important::
+   The :ref:`expenses/approve`, :ref:`expenses/post`, and :ref:`expenses/reimburse` sections are
+   **only** for users with the *necessary rights*.
+
+.. _expenses/approve:
+
+Approve expenses
+================
+
+In Odoo, not just anyone can approve expense reports— only users with the necessary rights (or
+permissions) can. This means that a user must have at least *Team Approver* rights for the
+*Expenses* app. Employees with the necessary rights can review expense reports, and approve or
+reject them, as well as provide feedback thanks to the integrated communication tool.
+
+To see who has rights to approve, go to the main :menuselection:`Settings` app and click on
+:guilabel:`Manage Users`.
+
+.. note::
+   If the *Settings* app is not available, then certain rights are not set on the account. In the
+   :guilabel:`Access Rights` tab of a user's card in the :menuselection:`Settings` app, the
+   :guilabel:`Administration` section is set to one of three options:
+
+   - :guilabel:`None (blank)`: The user cannot access the *Settings* app at all.
+   - :guilabel:`Access Rights`: The user can only view the :guilabel:`User's & Companies` section of
+     the *Settings* app.
+   - :guilabel:`Settings`: The user has access to the entire *Settings* app with no restrictions.
+
+   Please refer to :doc:`this document </applications/general/users/manage_users>` to learn more
+   about managing users and their access rights.
+
+Click on an individual to view their card, which displays the :guilabel:`Access Rights` tab in the
+default view. Scroll down to the :guilabel:`Human Resources` section. Under :guilabel:`Expenses`,
+there are four options:
+
+- :guilabel:`None (blank)`: A blank field means the user has no rights to view or approve expense
+  reports, and can only view their own.
+- :guilabel:`Team Approver`: The user can only view and approve expense reports for their own
+  specific team.
+- :guilabel:`All Approver`: The user can view and approve any expense report.
+- :guilabel:`Administrator`: The user can view and approve any expense report as well as access the
+  reporting and configuration menus in the *Expenses* app.
+
+Users who are able to approve expense reports (typically managers) can easily view all expense
+reports to validate. Go to :menuselection:`Expenses app --> Expense Reports  --> Reports to
+Approve`. This view lists all the expense reports that have been submitted but not approved, as
+noted by the :guilabel:`Submitted` tag in the status column.
+
+.. image:: expenses/reports-to-approve.png
+   :align: center
+   :alt: Reports to validate are found on the Reports to Approve page.
+
+Reports can be approved in two ways (individually or several at once) and refused only one way. To
+approve multiple expense reports at once, remain in the list view. First, select the reports to
+approve by clicking the check box next to each report, or click the box next to :guilabel:`Employee`
+to select all reports in the list. Next, click on the :guilabel:`⚙️ Action (gear)` icon, then click
+:guilabel:`Approve Report`.
+
+.. image:: expenses/approve-report.png
+   :align: center
+   :alt: Approve multiple reports by clicking the checkboxes next to each report.
+
+To approve an individual report, click on a report to go to a detailed view of that report. In this
+view, several options are presented: :guilabel:`Approve`, :guilabel:`Refuse`, or :guilabel:`Reset to
+draft`. Click :guilabel:`Approve` to approve the report.
+
+If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief explanation for the refusal
+in the :guilabel:`Reason to refuse Expense` field, then click :guilabel:`Refuse`.
+
+.. image:: expenses/refuse-expense.png
+   :align: center
+   :alt: Send messages in the chatter.
+
+Team managers can easily view all the expense reports for their team members. While in the
+:guilabel:`Reports to Approve` view, click on :guilabel:`Filters`, then click :guilabel:`My Team`.
+This presents all the reports for the manager's team.
+
+.. image:: expenses/my-team-filter.png
+   :align: center
+   :alt: Select the My Team filter.
+
+.. note::
+   If more information is needed, such as a receipt is missing, communication is easy from the
+   chatter. In an individual report, simply type in a message, tagging the proper person (if
+   needed), and post it to the chatter by clicking :guilabel:`Send`. The message is posted in the
+   chatter, and the person tagged will be notified via email of the message, as well as anyone
+   following.
+
+   .. image:: expenses/chatter.png
+      :align: center
+      :alt: Send messages in the chatter.
+
+.. _expenses/post:
+
+Post expenses in accounting
+===========================
+
+Once an expense report is approved, the next step is to post the report to the accounting journal.
+To view all expense reports to post, go to :menuselection:`Expenses --> Expense Reports --> Reports
+To Post`.
+
+.. image:: expenses/post-reports.png
+   :align: center
+   :alt: View reports to post by clicking on expense reports, then reports to post.
+
+Just like approvals, expense reports can be posted in two ways (individually or several at once). To
+post multiple expense reports at once, remain in the list view. First, select the reports to post by
+clicking the check box next to each report, or click the box next to :guilabel:`Employee` to select
+all reports in the list. Next, click on the :guilabel:`⚙️ Action (gear)` icon, then click
+:guilabel:`Post Entries`.
+
+.. image:: expenses/post-entries.png
+   :align: center
+   :alt: Post multiple reports from the Post Entries view.
+
+To post an individual report, click on a report to go to the detailed view of that report. In this
+view, several options are presented: :guilabel:`Post Journal Entries`, :guilabel:`Report In Next
+Payslip`, or :guilabel:`Refuse`. Click :guilabel:`Post Journal Entries` to post the report.
+
+If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief explanation for the refusal
+in the :guilabel:`Reason to refuse Expense` field, then click :guilabel:`Refuse`. Refused reports
+can be viewed by going to :menuselection:`Expenses app --> Expense Reports  --> All Reports`. This
+list shows all reports, including the refused ones.
+
+.. note::
+   To post expense reports to an accounting journal, the user must have following access rights:
+
+   - Accounting: Accountant or Adviser
+   - Expenses: Manager
+
+.. _expenses/reimburse:
+
+Reimburse employees
+===================
+
+After an expense report is posted to an accounting journal, the next step is to reimburse the
+employee. To view all expense reports to pay, go to :menuselection:`Expenses --> Expense Reports -->
+Reports To Pay`.
+
+.. image:: expenses/reports-to-pay.png
+   :align: center
+   :alt: View reports to pay by clicking on expense reports, then reports to pay.
+
+Just like approvals and posting, expense reports can be paid in two ways (individually or several at
+once). To pay multiple expense reports at once, remain in the list view. First, select the reports
+to pay by clicking the check box next to each report, or click the box next to :guilabel:`Employee`
+to select all reports in the list. Next, click on the :guilabel:`⚙️ Action (gear)` icon, then click
+:guilabel:`Register Payment`.
+
+.. image:: expenses/register-payment.png
+   :align: center
+   :alt: Post multiple reports by clicking the checkboxes, clicking the gear, then post the entries.
+
+To pay an individual report, click on a report to go to a detailed view of that report. Click
+:guilabel:`Register Payment` to pay the employee.
+
+Re-invoice expenses to customers
+================================
+
+If expenses are tracked on customer projects, expenses can be automatically charged back to the
+customer. This is done by creating an expense report, then creating a sales order with the expensed
+items on it. Then, managers approve the expense report, and the accounting department posts the
+journal entries. Finally, the customer is invoiced.
 
 Setup
 -----
 
--  Enable **Customer Billing** in the Expenses settings
+First, specify the invoicing policy for each expense product. Go to :menuselection:`Expenses app -->
+Configuration --> Expense Products`. Click on the expense product to edit, then click
+:guilabel:`Edit`. Under the :guilabel:`Invoicing` section, select the :guilabel:`Invoicing Policy`
+and :guilabel:`Re-Invoicing Policy` by clicking the radio button next to the desired selection.
 
--  Go to the product configuration menu and set the invoicing method on
-   all your Expense types:
+:guilabel:`Invoicing Policy`:
 
-   -  Ordered quantities: it will invoice expenses based on the ordered
-      quantity
+- :guilabel:`Ordered quantities`: Expense product will only invoice expenses based on the ordered
+  quantity.
+- :guilabel:`Delivered quantities`: Expense product will only invoice expenses based on the
+  delivered quantity.
 
-   -  Delivered quantities: it will invoice expenses based on the
-      expenses quantity
+:guilabel:`Re-Invoicing Policy`:
 
-   -  At cost: will invoice expenses at their real cost.
+- :guilabel:`No`: Expense product will not be re-invoiced.
+- :guilabel:`At cost`: Expense product will invoice expenses at their real cost.
+- :guilabel:`At sales price`: Expense product will invoice the price set on the sale order.
 
-   -  At sales price: will invoice based on a fixed sales price set on
-      the sale order.
+Create an expense
+-----------------
 
-.. image:: expenses/invoicing_01.png
-  :align: center
+First, when :ref:`creating a new expense <expenses/new>`, the correct information needs to be
+entered in order to re-invoice a customer. Select the :guilabel:`Customer to Reinvoice` from the
+drop-down menu. Next, select the :guilabel:`Analytic Account` the expense will be posted to.
 
-Create an order
----------------
+.. image:: expenses/reinvoice-expense.png
+   :align: center
+   :alt: Ensure the customer to be invoiced is called out on the expense.
 
--  As a salesman, create and confirm a Sales Order for the services
-   delivered to your customer. If you don't put any expense in the
-   order, it will be added automatically once posted by the
-   accountant.
+Create a quote and sales order
+------------------------------
 
--  Link the expense to the Sale Order.
+In the :menuselection:`Sales` app, create a quote for the customer being invoiced, listing the
+expense products. First, click :guilabel:`Create` to create a new quotation. Next, select the
+:guilabel:`Customer` being invoiced for the expenses from the drop-down menu.
 
-.. image:: expenses/invoicing_02.png
-  :align: center
+In the :guilabel:`Order Lines` tab, click :guilabel:`Add a product`. In the :guilabel:`Product`
+field, select the first item being invoiced from the drop-down menu, or type in the product name.
+Then, update the :guilabel:`Quantity`, the :guilabel:`Delivered` quantity, and the :guilabel:`Unit
+Price` if needed. Repeat this for all products being invoiced. When all the products have been added
+to the quote, click :guilabel:`Confirm` and the quotation becomes a sales order.
 
-Submit, validate and post expenses
-----------------------------------
+.. image:: expenses/expenses-salesorder.png
+   :align: center
+   :alt: Create and confirm the sales order with the expenses listed as products.
 
--  As a manager, make sure the analytic account is set on every expense
-   line on approving expenses reports. Click the line to add one if
-   missing. Employees are already able to set one when submitting.
+Once the quote turns into a sales order, a :guilabel:`Delivered` column appears. The delivered
+quantity must be updated for each item. Click on the `0.000` field for each product, and enter the
+delivered quantity. When all delivered quantities have been entered, click :guilabel:`Save`.
 
-.. image:: expenses/invoicing_03.png
-  :align: center
+Validate and post expenses
+--------------------------
 
--  As an accountant, post journal entries.
+Only employees with permissions (typically managers or supervisors) can :ref:`approve expenses
+<expenses/approve>`. Before approving an expense report, ensure the :guilabel:`Analytic Account` is
+set on every expense line of a report. If an :guilabel:`Analytic Account` is missing, click
+:guilabel:`Edit` and select the correct account from the drop-down menu, then click
+:guilabel:`Approve` or :guilabel:`Refuse`.
+
+The accounting department is typically responsible for :ref:`posting journal entries
+<expenses/post>`. Once an expense report is approved, it can then be posted.
 
 Invoice expenses
 ----------------
 
-Now you can invoice the order. It shows up in
-:menuselection:`Sales --> Invoicing --> Sales`
-to Invoice. The expenses have been added automatically in the order
-lines. Such items show up in blue (i.e. to invoice).
+Once the quote has turned into a sales order, and the expense report has been approved, it is time
+to invoice the customer. Go to :menuselection:`Sales app --> To Invoice --> Orders to Invoice` to
+view the sales orders ready to be invoiced.
 
-.. image:: expenses/invoicing_04.png
-  :align: center
-
-e (i.e. to invoice).
+Next, find the sales order related to the expense report, click into it, and then click
+:guilabel:`Create Invoice` and a :guilabel:`Create invoices` pop-up window appears. Select if the
+invoice is a :guilabel:`Regular invoice`, :guilabel:`Down payment (percentage)`, or :guilabel:`Down
+payment (fixed amount)` by clicking the radio button next to the selection. For either down payment
+options, enter the amount (fixed or percentage) in the :guilabel:`Down Payment Amount` field.
+Finally, click either :guilabel:`create and view invoice` or :guilabel:`create invoice`.

content/applications/finance/fiscal_localizations/mexico.rst

@@ -33,7 +33,7 @@ localization in Odoo, it is necessary to meet the following requirements:
    <https://www.gob.mx/sat/acciones-y-programas/certificado-de-sello-digital>`_ (CSD).
 #. Choose a PAC and purchase stamps. Currently the Mexican location in Odoo works with the following
    PACs: `Solución Factible <https://solucionfactible.com/>`_, `Quadrum (formerly Finkok)
-   <https://cfdiquadrum.com.mx/index.html>`_ and `SW Sapien - Smarter Web <https://sw.com.mx/>`_.
+   <https://cfdiquadrum.com.mx/index.html>`_ and `SW Sapien - Smarter Web <https://info.sw.com.mx/sw-smarter-odoo/>`_.
 #. Have knowledge and experience with billing, sales and accounting in Odoo. This documentation
    contains only the information necessary to enable the use of Odoo in a company based in Mexico.
 
@@ -211,7 +211,7 @@ working with and the credentials. That way, electronic invoicing will be enabled
    Remember that you must register directly with the PAC of your choice before you start creating
    invoices from Odoo. We have the following PACs available: `Quadrum
    <https://cfdiquadrum.com.mx/index.html>`_, `Solución Factible <https://solucionfactible.com/>`_
-   and `SW Sapien - Smarter Web <https://sw.com.mx/>`_.
+   and `SW Sapien - Smarter Web <https://info.sw.com.mx/sw-smarter-odoo/>`_.
 
    You must process your **Private Key (CSD)** with the SAT institution before following these
    steps. If you do not have this information, try with the Test Credentials and return to this

content/applications/finance/payment_acquirers/adyen.rst

@@ -47,8 +47,10 @@ API Key and Client Key
 
 In order to retrieve the API Key and the Client Key, log into your Adyen account, go to
 :menuselection:`Developers --> API Credentials`.
+
 - If you already have an API user, open it.
 - If you don't have an API user yet, click on **Create new credential**.
+
 Go to :menuselection:`Server settings --> Authentification` and copy or generate your **API Key**.
 Be careful to copy your API key as you'll not be allowed to get it later without generating a new
 one.
@@ -88,17 +90,32 @@ You have to save the webhook to finalize its creation.
 
 .. _adyen/urls:
 
-URLs
-~~~~
+API URLs
+~~~~~~~~
 
-To retrieve the URLs, log into your Adyen account, go to :menuselection:`Developers --> API URLs`.
-Select one of the URLs listed next to :guilabel:`Classic Recurring API` as your
-:guilabel:`Recurring API URL` and one listed next to :guilabel:`Checkout API` as your
-:guilabel:`Checkout API URL`.
+All Adyen API URLs include a customer area-specific prefix generated by Adyen. To configure the
+URLs, proceed as follows:
 
-.. image:: adyen/adyen-api-urls.png
-   :align: center
-   :alt: Get the links for the different API.
+#. Log into your Adyen account, then go to :menuselection:`Developers --> API URLs`.
+#. Copy the :guilabel:`Prefix` for your live Customer area (i.e., **data center**) and save it for
+   later.
+
+   .. image:: adyen/adyen-api-urls.png
+     :alt: Copy the prefix for the Adyen APIs
+
+#. In Odoo, :ref:`navigate to the payment acquirer Adyen <payment_acquirers/add_new>`.
+#. In the :guilabel:`Checkout API URL` field, enter the following URL and replace `yourprefix` with
+   the prefix you previously saved:
+   `https://yourprefix-checkout-live.adyenpayments.com/checkout`.
+#. In the :guilabel:`Recurring API URL` field, enter the following URL and replace `yourprefix` with
+   the prefix you previously saved:
+   `https://yourprefix-pal-live.adyenpayments.com/pal/servlet/Recurring`.
+
+.. note::
+   If you are trying Adyen as a test, you can use the following URLs instead:
+
+   - :guilabel:`Checkout API URL`: `https://checkout-test.adyen.com`
+   - :guilabel:`Recurring API URL`: `https://pal-test.adyen.com/pal/servlet/Recurring`
 
 Adyen Account
 -------------

content/applications/finance/payment_acquirers/paypal.rst

@@ -1,109 +1,82 @@
 ======
-Paypal
+PayPal
 ======
 
-`Paypal <https://www.paypal.com/>`_ is available and popular worldwide. It doesn't charge any
-subscription fee, and creating an account is very easy. That's why we recommend it for starters in
-Odoo. It works as a seamless flow where the customer is routed to the Paypal website to register the
-payment.
+`Paypal <https://www.paypal.com/>`_ is an American online payment acquirer available worldwide, and
+one of the few that does not charge a subscription fee.
 
-Settings in Odoo
-================
-
-.. seealso::
-   - :ref:`payment_acquirers/add_new`
-
-Credentials tab
----------------
-
-Odoo needs your **API Credentials** to connect with your PayPal account, which comprise:
-
-- **Email**: your login email address in Paypal.
-- **PDT Identity Token**: the key used to verify the authenticity of transactions.
-- **Use IPN**: whether you want to use Instant Payment Notification. Already checked, you don't have
-  to change it.
-
-You can copy your credentials from your Paypal account and paste them into the related fields under
-the **Credentials** tab.
-
-
-To set the **PDT Identity Token**, switch to :ref:`developer mode <developer-mode>` and retrieve the
-token by following the configuration step :ref:`paypal/enable-pdt`.
-
-.. important::
-   If you are trying Paypal as a test, using a :ref:`Paypal Sandbox account <paypal/testing>`,
-   change the **State** to *Test Mode*. We recommend doing this on a test Odoo database rather than
-   on your main database.
-
-Fees tab
---------
-
-You can charge extra fees to your customers for paying with Paypal to cover the transaction fees
-Paypal charges you. Once redirected to Paypal, your customer sees an extra amount applied to the
-order amount.
-
-To activate this, go to Paypal configuration's :guilabel:`Fees` tab in Odoo and activate
-:guilabel:`Add Extra Fees`.
-
-You can refer to `Paypal Fees <https://www.paypal.com/webapps/mpp/paypal-fees>`_ to set up fees.
-
-.. note::
-   `Traders in the EU <https://europa.eu/youreurope/citizens/consumers/shopping/pricing-payments/
-   index_en.htm>`_ are not allowed to charge extra fees for paying with credit cards.
-
-Settings in Paypal
+Settings in PayPal
 ==================
 
-First, set up your Paypal account to build a seamless customer experience with Odoo.
+To access your PayPal account settings, log into PayPal, open the :guilabel:`Account Settings`, and
+open the :guilabel:`Website payments` menu.
 
-Log into your PayPal account and open the account settings. Then, go to :menuselection:`Account menu
---> Account settings --> Website payments`.
+.. image:: paypal/paypal-account.png
+   :align: center
+   :alt: PayPal account menu
 
-Enable Auto Return
-------------------
+.. important::
+   Note that for PayPal to work **in Odoo**, the options :ref:`Auto Return <paypal/auto-return>`,
+   :ref:`PDT <paypal/pdt>`, and :ref:`IPN <paypal/ipn>` **must** all be enabled.
 
-The *Auto Return* feature automatically redirects your customers to Odoo once the payment is
-processed.
+.. _paypal/auto-return:
 
-From the *Website payments* settings page, go to :menuselection:`Website preferences --> Update -->
-Auto return for website payments` and select **On**. Enter the address of your Odoo database (e.g.,
-`https://yourcompany.odoo.com`) in the **Return URL** field.
+Auto Return
+-----------
+
+The **Auto Return** feature automatically redirects customers to Odoo once the payment is processed.
+
+From :guilabel:`Website payments`, go to :menuselection:`Website preferences --> Update --> Auto
+return for website payments --> Auto return` and select :guilabel:`On`. Enter the address of your
+Odoo database (e.g., `https://yourcompany.odoo.com`) in the :guilabel:`Return URL` field, and
+:guilabel:`Save`.
 
 .. note::
-   Any URL will do the job. Odoo only needs the setting to be enabled since it uses another URL.
+   Any URL does the job. Odoo only needs the setting to be enabled since it uses another URL.
 
-.. _paypal/enable-pdt:
+.. _paypal/pdt:
 
-Enable Payment Data Transfer (PDT)
+Payment Data Transfer (PDT)
+---------------------------
+
+:abbr:`PDT (Payment Data Transfer)` allows to receive payment confirmations, displays the payment
+status to the customers, and verifies the authenticity of the payments. From :menuselection:`Website
+preferences --> Update`, scroll down to :guilabel:`Payment data transfer` and select :guilabel:`On`.
+
+.. tip::
+   PayPal displays your **PDT Identity Token** as soon as :ref:`Auto return <paypal/auto-return>`
+   and :ref:`Payment Data Transfer (PDT) <paypal/pdt>` are enabled. If you need the **PDT Identity
+   Token**, disable and re-enable :guilabel:`Payment data transfer` to display the token again.
+
+.. _paypal/ipn:
+
+Instant Payment Notification (IPN)
 ----------------------------------
 
-Enable the *Payment Data Transfer* feature to receive payment confirmations immediately. This
-feature also displays the payment status to the customers and verifies the authenticity of the
-payments.
+:abbr:`IPN (Instant Payment Notifications)` is similar to **PDT**, but allows for more
+notifications, such as chargeback notifications. To enable **IPN**, go to :menuselection:`Website
+payments --> Instant payment notifications --> Update` and click :guilabel:`Choose IPN settings`.
+Enter a :guilabel:`Notification URL`, select :guilabel:`Receive IPN messages (Enabled)`, and
+:guilabel:`Save`.
 
-From the *Website payments* settings page, go to :menuselection:`Website preferences --> Update -->
-Payment data transfer` and select **On**. PayPal displays your **PDT Identity Token** as soon as
-the change is saved.
-
-Paypal Account Optional
+PayPal Account Optional
 -----------------------
 
-We advise you to not prompt customers to log in with a Paypal account when they get to pay. Let them
-pay with debit/credit cards as well, or you might lose some deals. Make sure this setting is turned
-on.
+We advise not to prompt customers to log in with a PayPal account upon payment. It is better and
+more accessible for customers to pay with a debit/credit card. To disable that prompt, go to
+:menuselection:`Account Settings --> Website payments --> Update` and select :guilabel:`On` for
+:guilabel:`PayPal account optional`.
 
 Payment Messages Format
 -----------------------
 
-Suppose you use accented characters (or anything else than primary Latin characters) for your
-customer names or addresses. In that case, you **must** configure the encoding format of the payment
-request sent by Odoo to Paypal. Otherwise, some transactions fail without notice.
+If you use accented characters (or anything other than primary Latin characters) for customer names
+or addresses, then you **must** configure the encoding format of the payment request sent by Odoo to
+PayPal. If you do not, some transactions fail without notice.
 
 To do so, go to `your production account <https://www.paypal.com/cgi-bin/customerprofileweb
-?cmd=_profile-language-encoding>`_. Then, click *More Options* and set the two default encoding
-formats as **UTF-8**.
-
-Your Paypal account is ready!
+?cmd=_profile-language-encoding>`_. Then, click :guilabel:`More Options` and set the two default
+encoding formats as :guilabel:`UTF-8`.
 
 .. tip::
    - For Encrypted Website Payments & EWP_SETTINGS error, please check the `Paypal documentation
@@ -113,6 +86,52 @@ Your Paypal account is ready!
      `link <https://sandbox.paypal.com/cgi-bin/customerprofileweb?cmd=_profile-language-encoding>`_
      to configure the encoding format in a test environment.
 
+Settings in Odoo
+================
+
+.. seealso::
+   :ref:`payment_acquirers/add_new`
+
+Credentials
+-----------
+
+Odoo needs your **API Credentials** to connect with your PayPal account. To do so, go to
+:menuselection:`Accounting --> Configuration --> Payment Acquirers` and :guilabel:`Activate` PayPal.
+Then, enter your PayPal account credentials in the :guilabel:`Credentials` tab:
+
+- :guilabel:`Email`: the login email address in Paypal;
+- :guilabel:`PDT Identity Token`: the key used to verify the authenticity of transactions;
+- :guilabel:`Use IPN`: enable for PayPal to work properly in Odoo.
+
+.. tip::
+   Save the :guilabel:`PDT Identity Token` for later use.
+
+To set the :guilabel:`PDT Identity Token`, switch to :ref:`developer mode <developer-mode>` and
+retrieve the token by following the configuration steps at :ref:`paypal/pdt`.
+
+.. note::
+   The PayPal **Merchant ID** is not required in Odoo.
+.. important::
+   If you are trying PayPal as a test, using a :ref:`PayPal Sandbox account <paypal/testing>`,
+   change the :guilabel:`State` to :guilabel:`Test Mode`. We recommend doing this on a test Odoo
+   database rather than on your main database.
+
+Extra fees
+----------
+
+You can charge **extra fees** to customers choosing to pay with PayPal in order to cover the
+transaction fees PayPal charges you. Once redirected to Paypal, your customer sees an extra amount
+applied to the order amount.
+
+To activate this option, go to :menuselection:`Accounting --> Configuration --> Payment Acquirers`
+and select :guilabel:`PayPal`. Then, go to the :guilabel:`Fees` tab and tick the :guilabel:`Add
+Extra Fees` box.
+
+.. note::
+   -  You can refer to `Paypal Fees <https://www.paypal.com/webapps/mpp/paypal-fees>`_ to set up
+      fees.
+   - `Traders in the EU <https://europa.eu/youreurope/citizens/consumers/shopping/pricing-payments/index_en.htm>`_ are not allowed to charge extra fees for paying with credit cards.
+
 .. _paypal/testing:
 
 Test environment
@@ -121,19 +140,21 @@ Test environment
 Configuration
 -------------
 
-Thanks to Paypal Sandbox accounts, you can test the entire payment flow in Odoo.
+Thanks to PayPal sandbox accounts, you can test the entire payment flow in Odoo.
 
-Log into the `Paypal Developer Site <https://developer.paypal.com/>`_ using your Paypal
-credentials, which creates two sandbox accounts:
+Log into the `Paypal Developer Site <https://developer.paypal.com/>`_ using your PayPal credentials,
+which creates two sandbox accounts:
 
 -  A business account (to use as merchants, e.g.,
-   `pp.merch01-facilitator@example.com <mailto:pp.merch01-facilitator@example.com>`_).
+   `pp.merch01-facilitator@example.com <mailto:pp.merch01-facilitator@example.com>`_);
 -  A default personal account (to use as shoppers, e.g.,
    `pp.merch01-buyer@example.com <mailto:pp.merch01-buyer@example.com>`_).
 
-Log into Paypal Sandbox using the merchant account and follow the same configuration instructions.
-Enter your sandbox credentials in Odoo and ensure Paypal is set on *Test Mode*. We recommend doing
-this on a test Odoo database rather than your main database.
+Log into PayPal sandbox using the merchant account and follow the same configuration instructions.
+Enter your sandbox credentials in Odoo (:menuselection:`Accounting --> Configuration --> Payment
+Acquirer --> PayPal` in the :guilabel:`Credentials` tab, and make sure the status is set on
+:guilabel:`Test Mode`. We recommend doing this on a test Odoo database rather than your main
+database.
 
 Run a test transaction from Odoo using the sandbox personal account.
 

content/applications/inventory_and_mrp/inventory/management/shipments_deliveries/receipts_delivery_two_steps.rst

@@ -32,7 +32,7 @@ Configure multi-step routes
 ===========================
 
 First, make sure the :guilabel:`Multi-Step Routes` option is enabled in :menuselection:`Inventory
---> Configuration --> Settings`, under the ::guilabel:`Warehouse` heading. After enabling the
+--> Configuration --> Settings`, under the :guilabel:`Warehouse` heading. After enabling the
 setting, :guilabel:`Save` the changes.
 
 .. note::
@@ -60,7 +60,7 @@ Shipments`. :guilabel:`Save` the changes to finish.
    by default, are labeled :guilabel:`WH/Input` and :guilabel:`WH/Output`, respectively, on the
    :guilabel:`Locations` dashboard. To rename these locations, go to :menuselection:`Configuration
    --> Locations`, select the :guilabel:`Location` to change, and then click :guilabel:`Edit`. On
-   the location form, update the ::guilabel:`Location Name`, make any other changes (if necessary)
+   the location form, update the :guilabel:`Location Name`, make any other changes (if necessary)
    and :guilabel:`Save` the changes.
 
 Process a receipt in two steps (input + stock)
@@ -76,12 +76,12 @@ quote as a new purchase order.
 
 .. important::
    For businesses with multiple warehouses that have different step configurations, the
-   :guilabel:`Deliver To` field on the ::abbr:`PO (Purchase Order)` form may need to be specifed as
+   :guilabel:`Deliver To` field on the :abbr:`PO (Purchase Order)` form may need to be specified as
    the correct *input location* connected to the two-step warehouse, which can be done by selecting
    the warehouse from the drop-down selection that includes the `Receipts` label at the end of the
    name.
 
-After confirming the ::abbr:`PO (Purchase Order)`, a :guilabel:`Receipt` smart button will appear in
+After confirming the :abbr:`PO (Purchase Order)`, a :guilabel:`Receipt` smart button will appear in
 the top-right corner of the :abbr:`PO (Purchase Order)` form — click it to reveal the associated
 receipt.
 
@@ -90,8 +90,8 @@ receipt.
    :alt: After confirming a purchase order, a Receipt smart button will appear.
 
 .. tip::
-   Purchase order receipts can also be found in the :menuselection:`Inventory` application. In
-   the :guilabel:`Overview` dashboard, click the :guilabel:`# to Process` smart button in the
+   Purchase order receipts can also be found in the :menuselection:`Inventory` application. In the
+   :guilabel:`Overview` dashboard, click the :guilabel:`# to Process` smart button in the
    :guilabel:`Receipts` kanban card.
 
    .. image:: receipts_delivery_two_steps/two-step-receipts-kanban.png
@@ -143,12 +143,12 @@ Create a sales order
 --------------------
 
 In the :menuselection:`Sales` application, create a new quote by clicking :guilabel:`Create`. Select
-(or create) a :guilabel:`Customer`, add a storable :guilabel:`Product` to the order lines, and then
+or create a :guilabel:`Customer`, add a storable :guilabel:`Product` to the order lines, and then
 click :guilabel:`Confirm`.
 
-After confirming the ::abbr:`SO (Sales Order)`, a :guilabel:`Receipt` smart button will appear in
-the top-right corner of the :abbr:`PO (Sales Order)` form — click it to reveal the associated
-receipt.
+After confirming the :abbr:`SO (Sales Order)`, a :guilabel:`Delivery` smart button will appear in
+the top-right corner of the :abbr:`SO (Sales Order)` form. Click it to reveal the associated
+delivery forms.
 
 .. image:: receipts_delivery_two_steps/two-step-sales-quote.png
    :align: center
@@ -168,8 +168,8 @@ Process the picking
 -------------------
 
 The picking and delivery order will be created once the sales order is confirmed. When the
-:guilabel:`Delivery` smart button appears, click it to arrive to the :guilabel:`Transfers`
-dashboard, which lists both the picking and the delivery orders.
+:guilabel:`Delivery` smart button appears, click it to reveal the :guilabel:`Transfers` dashboard,
+which lists both the picking and the delivery orders.
 
 The status of the picking will be :guilabel:`Ready`, since the product must be picked from stock
 before it can be shipped. The status of the delivery order will be :guilabel:`Waiting Another
@@ -201,8 +201,8 @@ the :guilabel:`# To Process` smart button in the :guilabel:`Delivery Orders` kan
 
 .. tip::
    The delivery order associated with the :abbr:`SO (Sales Order)` can also be quickly accessed by
-   clicking on the ::guilabel:`Delivery` smart button again, and choosing the delivery order on the
-   ::guilabel:`Transfers` page (which should now be marked as ::guilabel:`Ready`).
+   clicking on the :guilabel:`Delivery` smart button again, and choosing the delivery order on the
+   :guilabel:`Transfers` page (which should now be marked as :guilabel:`Ready`).
 
 .. image:: receipts_delivery_two_steps/deliver-two-step-kanban.png
    :align: center
@@ -217,5 +217,5 @@ Click on the delivery order associated with the :abbr:`SO (Sales Order)`, then c
          the customer location.
 
 Once the delivery order is validated, the product leaves the :guilabel:`WH/Output` location on the
-:guilabel:`Transfers` dashboard and moves to the :guilabel:`Partners/Customers` location. Then,
-the status of the document will change to :guilabel:`Done`.
+:guilabel:`Transfers` dashboard and moves to the :guilabel:`Partners/Customers` location. Then, the
+status of the document will change to :guilabel:`Done`.

content/applications/marketing/marketing_automation/getting_started/target_audience.rst

@@ -2,16 +2,17 @@
 Target an audience
 ==================
 
-Delivering marketing campaigns to the *right* audience is paramount when trying to grow a business.
-The :guilabel:`Odoo Marketing Automation` application helps marketers to do just that by providing
-filtering tools, that can be as simple or as complex as necessary, to reach the right customers at
-the right time.
+Delivering marketing campaigns to the right audience is paramount when trying to grow a business.
+The Odoo *Marketing Automation* application helps marketers to do just that by providing detailed
+filtering tools, which can be as simple (or as complex) as necessary, to reach the right customers
+at the right time.
 
-Work with target filters
+Configure target filters
 ========================
 
-When configuring the filters on a marketing campaign, there are some options that have an arrow
-icon beside them. The arrow signifies that the filter has more refined parameters within it.
+When configuring the target filters on a marketing campaign, there are some options that have an
+:guilabel:`> (arrow)` icon beside them. The :guilabel:`> (arrow)` icon signifies that the particular
+filter has more refined parameters within it that can be customized.
 
 .. image:: target_audience/marketing-filters.png
    :align: center
@@ -19,22 +20,22 @@ icon beside them. The arrow signifies that the filter has more refined parameter
 
 Filters can be extended by adding *branches* and *nodes*. A *node* adds another filtering parameter
 to a group of targeting conditions (e.g. a new line), and a *branch* creates a narrowly refined
-cluster of parameters, allowing filters to be grouped with *Any* or *All* statements.
+cluster of parameters, allowing filters to be grouped with :guilabel:`ANY` or :guilabel:`ALL`
+statements.
 
 Every time a new branch is created, there are two options:
 
-- Either the records can match :guilabel:`ALL` criteria for the upcoming rules (an AND statement
-  where all criteria must match).
-
-- Or, the records can match :guilabel:`ANY` criteria for the upcoming rules (an OR statement where
-  only one of the criteria must match).
+- Either the records can match :guilabel:`ALL` criteria for the upcoming rules (creating an AND
+  statement where *all* criteria must match).
+- Or, the records can match :guilabel:`ANY` criteria for the upcoming rules (creating an OR
+  statement where *only one* of the criteria must match).
 
 To change between these two options, simply click the drop-down arrow icon in the green box and
-select :guilabel:`Any` or :guilabel:`All`.
+select :guilabel:`ANY` or :guilabel:`ALL`.
 
-To add a node, click on the :guilabel:`+ (plus sign icon)` and to add another branch click on the
-:guilabel:`... (ellipses icon)`. To exclude a :guilabel:`node` (or a :guilabel:`branch`), click on
-:guilabel:`x (delete)`.
+To add a node, click on the :guilabel:`➕ (plus sign)` icon, and to add another branch click on the
+:guilabel:`⋯ (ellipses)` icon. To exclude a node or a branch, click on :guilabel:`✖ (delete)` icon
+to delete it.
 
 .. image:: target_audience/marketing-filter-nodes.png
    :align: center
@@ -43,78 +44,79 @@ To add a node, click on the :guilabel:`+ (plus sign icon)` and to add another br
 Use cases
 =========
 
-The following scenarios below outline different combinations of filters a marketing campaign might
+The following scenarios outline different combinations of filters a marketing campaign might
 commonly use.
 
-Scenario #1: Narrow the target down to new opportunities in the pipeline
-------------------------------------------------------------------------
+Scenario #1: Narrow target down to new opportunities in the pipeline
+--------------------------------------------------------------------
 
-While in Edit mode on a campaign template form, select the :guilabel:`Target` field, and click
-:guilabel:`Search More` from the drop-down menu. Then, search for :guilabel:`Lead/Opportunity` and
-select it.
+While in *Edit mode* on a campaign template form (by clicking the :guilabel:`Edit` button), select
+the :guilabel:`Target` field, and click :guilabel:`Search More` from the drop-down menu. Then,
+search for :guilabel:`Lead/Opportunity`, and select it.
 
-Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Click on the default
+Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Then, click on the default
 :guilabel:`ID` filter option in the first portion of the filter equation. Doing so reveals a
 drop-down menu full of filter options. From this drop-down, scroll down (or search for)
 :guilabel:`Type`.
 
-Keep the second portion of the filter equation on the default :guilabel:`= (equal sign)`.
+Keep the second portion of the filter equation on the default :guilabel:`🟰 (equal sign)` icon.
 
-Then, change the third (and final) portion of the filter equation from :guilabel:`Lead` to
+Next, change the third (and final) portion of the filter equation from :guilabel:`Lead` to
 :guilabel:`Opportunity`. The number of :guilabel:`Records` that fit this specific filter equation
-will change as the equation is customized.
+changes as the equation is customized.
 
-Add another node to this filter by clicking the :guilabel:`+ (plus sign)` to the right of the
+Add another node to this filter by clicking the :guilabel:`➕ (plus sign)` icon to the right of the
 equation.
 
-With "new" opportunities being the target of this filter, the second node will focus on only
+With "new" opportunities being the target of this filter, the second node will focus on *only*
 locating opportunities that are in the :guilabel:`New` stage of the pipeline. To do that, select
-the default :guilabel:`ID` from the first portion of the second filter equation, and scroll down
-(or search for) :guilabel:`Stage` from the field drop-down menu.
+the default :guilabel:`ID` from the first portion of the second filter equation, and scroll down (or
+search for) :guilabel:`Stage` from the field drop-down menu.
 
-Once again, leave the second portion of the filter equation on :guilabel:`= (equal sign)`.
+Once again, leave the second portion of the filter equation on :guilabel:`🟰 (equal sign)` icon.
 
-Lastly, highlight the default value in the third (and final) portion of the second filter equation
-and type in :guilabel:`New`. With that completed, Odoo will only target opportunities that are in
-the "New" stage of the pipeline.
+Lastly, highlight the default value in the third (and final) portion of the second filter equation,
+and type in `New`. With that in place, Odoo only targets opportunities that are in the "New" stage
+of the pipeline.
 
 .. image:: target_audience/filters-opportunities.png
    :align: center
    :alt: A standard scenario using filters in the Odoo Marketing Automation app.
 
-Scenario #2: Narrow the target down to the event attendees that purchased a specific ticket
--------------------------------------------------------------------------------------------
+Scenario #2: Narrow down target to event attendees who purchased a specific ticket
+----------------------------------------------------------------------------------
 
-While in Edit mode on a campaign template form, select the :guilabel:`Target` field, and click
-:guilabel:`Search More` from the drop-down menu. Then, scroll down (or search for)
-:guilabel:`Event` and select it.
+While in *Edit mode* on a campaign template form (by clicking the :guilabel:`Edit` button), select
+the :guilabel:`Target` field, and click :guilabel:`Search More` from the drop-down menu. Then,
+scroll down (or search for) :guilabel:`Event`, and select it.
 
 Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Click on the default
 :guilabel:`ID` filter option in the first portion of the filter equation. Doing so reveals a
 drop-down menu full of filter options. From this drop-down, scroll down (or search for)
 :guilabel:`Event`.
 
-Click the the default :guilabel:`= (equal sign)` in the second portion of the filter equation.
-This reveals a drop-down menu. On this menu, select :guilabel:`contains`.
+Click the default :guilabel:`🟰 (equal sign)` icon in the second portion of the filter equation. This
+reveals a drop-down menu. From this drop-down menu, select :guilabel:`contains`.
 
-In the third (and final) empty portion of the filter equation, type in the name of the event(s)
-that you would like Odoo to consider for this campaign filter.
+In the third (and final) empty portion of the filter equation, type in the name of the event(s) that
+Odoo should consider for this campaign filter.
 
-Add another node to this filter by clicking the :guilabel:`+ (plus sign)` to the right of the
-equation.
+Then, add another node to this filter by clicking the :guilabel:`➕ (plus sign)` icon to the right of
+the equation.
 
 The second node will focus on targeting this campaign to attendees who purchase a specific type of
-ticket to the aforementioned event(s) in the first filter equation. To do that, select the default
-:guilabel:`ID` from the first portion of the second filter equation, and scroll down (or search
-for) :guilabel:`Event Ticket` from the field drop-down menu. Then, in that same drop-down menu,
-select :guilabel:`Name`.
+ticket to the aforementioned event(s) mentioned in the first filter equation.
 
-Once again, click the the default :guilabel:`= (equal sign)` in the second portion of the filter
+To do that, select the default :guilabel:`ID` from the first portion of the second filter equation,
+and scroll down (or search for) :guilabel:`Event Ticket` from the field drop-down menu. Then, in
+that same drop-down menu, select :guilabel:`Name`.
+
+Once again, click the default :guilabel:`🟰 (equal sign)` icon in the second portion of the filter
 equation, and select :guilabel:`contains`.
 
-Lastly, in the third (and final) portion of the second filter equation, which will be blank, type
-in the name of the ticket type that should be used for the filter. In this case,
-:guilabel:`Standard` is the name of the event ticket type for this sample filter.
+Lastly, in the third (and final) portion of the second filter equation, which is blank, type in the
+name of the ticket type that should be used for the filter. In this case, :guilabel:`Standard` is
+the name of the event ticket type for this sample filter.
 
 .. image:: target_audience/filters-event-ticket.png
    :align: center

content/applications/marketing/marketing_automation/getting_started/testing_running.rst

@@ -1,41 +1,52 @@
-==============================
-Testing and running a campaign
-==============================
+=========================
+Testing/running campaigns
+=========================
 
 Odoo gives users the ability to test marketing campaigns (and mailings) before officially running
 them.
 
-First, open the :guilabel:`Marketing Automation` application and click on a campaign. Make sure
-the campaign already has activities configured on it (or build a campaign by following the
-directions here on :doc:`this documentation <workflow_activities>`). To start a test, click the
-:guilabel:`Launch a Test` button at the top of the template form.
+First, open the :menuselection:`Marketing Automation` application, and select the desired campaign,
+which reveals that campaign's detail form.
+
+On the campaign detail form, make sure the campaign already has activities configured (or build a
+campaign by following the directions here on :doc:`this documentation
+</applications/marketing/marketing_automation/getting_started/workflow_activities>`).
+
+To start a test, click the :guilabel:`Launch a Test` button at the top of the campaign form.
 
 .. image:: testing_running/launch-test.png
    :align: center
    :alt: Launch a test button in Odoo Marketing Automation.
 
-When clicked, a pop-up window appears. In the dropdown field choose a specific record to run the
-test on, or create a brand new record by clicking the :guilabel:`Search More...` link at the bottom
-of the dropdown menu, and then click the :guilabel:`Create` button.
+When clicked, a :guilabel:`Launch a test` pop-up window appears. In the drop-down field, choose an
+existing record (or create a new one) to run the test on. To create a brand new record, click the
+:guilabel:`Search More...` link at the bottom of the drop-down menu, and then click the
+:guilabel:`Create` button.
 
-Once the record is selected, click :guilabel:`Continue`, and Odoo will redirect to the campaign
-test page.
+Doing so reveals a blank contact form, in which the :guilabel:`Name` and :guilabel:`Email` **must**
+be entered. When all the necessary information has been entered, click :guilabel:`Save`, and Odoo
+returns to the :guilabel:`Launch a test` pop-up, with that new record in the :guilabel:`Choose an
+existing record or create a new one to test` field.
+
+Once a record is selected, click :guilabel:`Continue`, and Odoo reveals the campaign test page.
 
 .. image:: testing_running/test-screen.png
    :align: center
    :alt: Test screen in Odoo Marketing Automation.
 
-Here, the name of the :guilabel:`Record` being tested is visible, along with the precise time this
-test workflow was started. Beneath that is the first activity (or activities) in the workflow.
+On the campaign test page, the name of the :guilabel:`Record` being tested is visible, along with
+the precise time this test workflow was started in the :guilabel:`Workflow Started On` field.
+Beneath that, in the :guilabel:`Workflow` section is the first activity (or activities) in the
+workflow that's being tested.
 
-To start a test, click the :guilabel:`Run` icon beside the first activity in the workflow. When
-clicked, the page will reload, and Odoo will show the various results (and analytics) connected to
-that specific activity.
+To start a test, click the :guilabel:`Run` button, represented by a :guilabel:`▶️ (play button)`
+icon beside the first activity in the workflow. When clicked, the page reloads, and Odoo shows the
+various results (and analytics) connected to that specific activity as they occur, in real-time.
 
 .. image:: testing_running/workflow-test-progress.png
    :align: center
    :alt: Workflow test progress in Odoo Marketing Automation.
 
-Once all the workflow activities are completed, the test will end and be moved to the
+Once all the workflow activities are completed, the test will end, and move to the
 :guilabel:`Completed` stage. To stop a test before all the workflow activities are completed, click
-the :guilabel:`Stop` button.
+the :guilabel:`Stop` button in the upper-left corner of the campaign test page.

content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst

@@ -2,44 +2,51 @@
 Marketing activities
 ====================
 
-When creating a campaign in the :guilabel:`Marketing Automation` app, users can plan marketing
-activities such as email or SMS campaigns. To get started, navigate to the :guilabel:`Workflow`
-area, and click :guilabel:`Add New Activity`. A blank activity template will appear where
-parameters can be set for that specific activity.
+When creating a campaign in the *Marketing Automation* app, users can plan marketing activities,
+such as email or SMS campaigns.
 
-When :guilabel:`Add New Activity` is selected, a blank activity template will appear with the
-following customizable fields:
+To get started, navigate to the bottom of a marketing automation campaign detail form, and click
+:guilabel:`Add New Activity`. Doing so reveals a :guilabel:`Create Activities` pop-up window. This
+pop-up window is a blank activity template, where specific parameters can be set for that particular
+activity.
+
+The following fields are available in the :guilabel:`Create Activities` pop-up window (when
+:guilabel:`Add New Activity` is clicked):
 
 .. image:: workflow_activities/activity-template.png
    :align: center
    :alt: An activity template in Odoo Marketing Automation.
 
 - :guilabel:`Activity Name`: the title of the activity.
-- :guilabel:`Activity Type`: choose between Email, Server Action (internal Odoo operation), or SMS.
+- :guilabel:`Activity Type`: choose between `Email`, `Server Action` (internal Odoo operation), or
+  `SMS`.
 - :guilabel:`Mail Template`: choose from pre-configured templates (or create a new one on-the-fly).
 - :guilabel:`Trigger`: choose when this activity should be triggered.
 - :guilabel:`Expiry Duration`: configure to stop the actions after a specific amount of time (after
   the scheduled date). When selected, a :guilabel:`Cancel after` field appears, in which the user
-  can choose how many :guilabel:`Hours, Days, Weeks, or Months` they want the actions to cease
-  after the initial date.
-- :guilabel:`Activity Filter`: domain related to this activity (and all subsequent Child
-  Activities).
-- :guilabel:`Applied Filter`: activity will *only* be performed if it satisfies the specified
-  domain (filter).
+  can choose how many :guilabel:`Hours, Days, Weeks, or Months` they want the actions to cease after
+  the initial date.
+- :guilabel:`Activity Filter`: domain related to this activity (and all subsequent child
+  activities).
+- :guilabel:`Applied Filter`: activity will *only* be performed if it satisfies the specified domain
+  (filter).
 
-After the activity's settings are fully configured, click :guilabel:`Save & Close` to finish
-creating the activity.
+After the activity's settings are fully configured, click :guilabel:`Save & Close` to save the
+activity and return to the marketing automation campaign form, :guilabel:`Save & New` to save the
+activity and immediately create another one in a fresh :guilabel:`Create Activities` pop-up window,
+or :guilabel:`Discard` to delete the activity and return to the marketing automation campaign form.
 
 Workflow activity
 =================
 
-Once saved, the :guilabel:`Workflow Activity` will appear in Odoo, where each activity will be
-shown as a graph by default. The configured trigger time for that activity can be found to the left
-of the :guilabel:`Workflow Activity` card.
+Once an activity is saved, the :guilabel:`Workflow Activity` section appears at the bottom of the
+marketing automation campaign form. Each activity is displayed as a line graph.
 
-In the :guilabel:`Workflow Activity` section, there is also the number of activities that are
-successful or rejected. The :guilabel:`Success` and :guilabel:`Rejected` numbers are color-coded
-in the graph for easy reference (in green and red, respectively).
+The configured :guilabel:`Trigger` time for that activity can be found to the left of the
+:guilabel:`Workflow Activity` card in the :guilabel:`Workflow` section.
+
+Once the activity has been triggered, a figure representing the number of :guilabel:`Success` or
+:guilabel:`Rejected` activities will be displayed to the right of the graph.
 
 .. image:: workflow_activities/workflow-activity.png
    :align: center
@@ -47,20 +54,23 @@ in the graph for easy reference (in green and red, respectively).
 
 .. tip::
    If the :guilabel:`Activity Type` of the activity is set to :guilabel:`Email`, there are more
-   in-depth analytics beneath the :guilabel:`Workflow Activity` data detailing how many emails have
-   been :guilabel:`Sent`, and what percentage of those have been :guilabel:`Clicked`,
-   :guilabel:`Replied` to, or :guilabel:`Bounced`.
+   in-depth analytics beneath the activity graph data, detailing how many emails have been
+   :guilabel:`Sent`, and what percentage of those have been :guilabel:`Clicked`, :guilabel:`Replied`
+   to, or :guilabel:`Bounced`.
 
 Child activities
 ================
 
-Odoo also has the option to :guilabel:`Add Child Activity`. *Child Activities* are sub-activities
-that are connected to (and triggered by) the activity above it, which is also known as its *Parent
-Activity*.
+There is also the option to add a *child activity* by clicking :guilabel:`Add child activity`,
+located at the bottom of each activity block in the :guilabel:`Workflow` section of a marketing
+automation form.
 
-Odoo provides a number of triggering options to launch a :guilabel:`Child Activity` - all of which
-depend on the trigger configurations related to the parent activity. Under the desired parent
-activity, hover over :guilabel:`Add child activity`, and select the trigger:
+Child activities are sub-activities that are connected to (and triggered by) the activity above it,
+which is also known as its *parent activity*.
+
+Odoo provides a number of triggering options to launch a child activity - all of which depend on the
+trigger configurations related to the parent activity. Under the desired parent activity, hover over
+:guilabel:`Add child activity`, and select any of the following triggers:
 
 - :guilabel:`Add Another Activity`: instantly add another activity.
 - :guilabel:`Opened`: the next activity will be triggered if the (email) recipient opens the
@@ -76,6 +86,7 @@ activity, hover over :guilabel:`Add child activity`, and select the trigger:
   link included in the mailing.
 - :guilabel:`Bounced`: the next activity will be triggered if the mailing is bounced (not sent).
 
-Once a trigger is selected, the user can configure the child activity (it has the same
-configuration options as a regular activity) and click :guilabel:`Save & Close`` to finish creating
-the child activity.
+Once a trigger is selected, the user can configure the child activity (it has the same configuration
+options as a regular activity), and click :guilabel:`Save & Close` to finish creating the child
+activity, which will then be displayed in the :guilabel:`Workflow` section, in a slightly indented
+position beneath its parent activity.

content/applications/productivity/discuss/advanced/ice_servers.rst

@@ -10,7 +10,7 @@ calls, and then, connect that Twilio account to Odoo.
 Create a Twilio account
 =======================
 
-First, go to `Twilio <https://www.twilio.com_>`_ and click :guilabel:`Sign up` to create a new
+First, go to `Twilio <https://www.twilio.com>`_ and click :guilabel:`Sign up` to create a new
 Twilio account. Next, enter your name and email address, create a password, and accept Twilio's
 terms of service. Then, click :guilabel:`Start your free trial`. Verify your email address with
 Twilio, as per their instructions.

content/applications/sales/point_of_sale.rst

@@ -23,17 +23,17 @@ Control` screen, click :guilabel:`Open Session` to start a POS session, or click
 Selling` if the session is already opened.
 
 .. note::
-   Multiple users can be connected to the same session at the same time. However, the session can
-   only be opened once on the same browser.
+   :doc:`Multiple users <point_of_sale/employee_login>` can be logged into the same session at the
+   same time. However, the session can only be opened once on the same browser.
 
 .. _pos/sell:
 
 Sell products
 =============
 
-Click products to add them to the cart. To change the **quantity**, click :guilabel:`Qty` and enter
-the number of products using the keypad. To add a **discount** or modify the product **price**,
-click respectively :guilabel:`Disc` or :guilabel:`Price` and enter the amounts.
+Click on products to add them to the cart. To change the **quantity**, click :guilabel:`Qty` and
+enter the number of products using the keypad. To add a **discount** or modify the product
+**price**, click respectively :guilabel:`Disc` or :guilabel:`Price` and enter the amounts.
 
 Once an order is completed, proceed to checkout by clicking :guilabel:`Payment`. Select the
 **payment method**, enter the received amount, and click :guilabel:`Validate`. Click
@@ -49,28 +49,18 @@ Once an order is completed, proceed to checkout by clicking :guilabel:`Payment`.
 
 .. _pos/customers:
 
-Register customers
-==================
+Set customers
+=============
 
-Registering your customers gives you the ability to grant them various privileges such as discounts,
-loyalty program, specific communication. It is also required if they want an invoice and registering
-them makes any future interaction with them faster.
+You can create and set customers from an :ref:`open POS session <pos/session-start>`. Registering
+your customer is necessary to :doc:`collect their loyalty points and grant them rewards
+<point_of_sale/pricing/loyalty>`, automatically apply the :doc:`attributed pricelist
+<point_of_sale/pricing/pricelists>`, or :ref:`generate and print an invoice
+<receipts-invoices/invoices>`.
 
-From your session interface, use the customer button.
-
-.. image:: point_of_sale/customer-button.png
-
-Create a new one by using this button.
-
-.. image:: point_of_sale/customer-add.png
-
-You will be invited to fill out the customer form with their
-information.
-
-.. image:: point_of_sale/customer-form.png
-
-Use the save button when you are done. You can then select that customer
-in any future transactions.
+To access the list of customers, click :guilabel:`Customer` on the POS interface. Then, select a
+customer or create a new one by clicking :guilabel:`Create`, completing the form, and saving.
+Lastly, click :guilabel:`Set Customer` to set the selected customer.
 
 .. _pos/customer-notes:
 

content/applications/sales/point_of_sale/payment_methods.rst

@@ -11,28 +11,20 @@ to allow this payment method *exclusively* for registered customers.
 Then, select the :guilabel:`Journal`. Choose :guilabel:`Cash` to use this payment method for cash
 payments, or :guilabel:`Bank` to use it for card payments.
 
-.. comment:
-   when created, add a link to the customeraccount page under advanced_pricing_features
-
 .. image:: payment_methods/payment-method.png
    :alt: Creating a new payment method for a POS.
 
 .. note::
-   - Selecting a :guilabel:`bank` journal automatically adds the :guilabel:`Use a Payment Terminal`
-     field in which you can add your terminal's information.
-   - Credentials are mandatory to use a payment terminal. To learn how to configure the different
-     terminals, check out the following documentation pages:
+   Selecting a :guilabel:`bank` journal automatically adds the :guilabel:`Use a Payment Terminal`
+   field in which you can add your :doc:`payment terminal's information
+   <payment_methods/terminals>`.
 
-     - :doc:`Adyen configuration <payment_methods/terminals/adyen>`
-     - :doc:`Vantiv configuration <payment_methods/terminals/vantiv>`
-     - :doc:`Ingenico configuration <payment_methods/terminals/ingenico>`
-     - :doc:`Six configuration <payment_methods/terminals/six>`
-     - :doc:`Worldline configuration <payment_methods/terminals/worldline>`
+.. seealso::
+   :doc:`payment_methods/terminals`.
 
-Once the payment method is created, you can select it in your POS settings. To do so, go to
-:menuselection:`Point of Sale --> Configuration --> Point of Sale` and select a POS for which you
-wish to make the payment method available. Click :guilabel:`Edit` and add the payment method under
-the :guilabel:`Payments` section.
+Once the payment method is created, you can select it in your POS settings. To do so, go to the
+:ref:`POS' settings <configuration/settings>`, click :guilabel:`Edit`, and add the payment method
+under the :guilabel:`Payments` section.
 
 .. toctree::
    :titlesonly:

content/applications/sales/point_of_sale/payment_methods/terminals.rst

@@ -1,9 +1,32 @@
-:nosearch:
+:show-content:
 
 =================
 Payment terminals
 =================
 
+Connecting and integrating a payment terminal with your POS system allows you to accept multiple
+payment options, including credit and debit cards, making the payment process more efficient.
+
+Configuration
+=============
+
+Go to the :doc:`application settings <../configuration>`, scroll down to the :guilabel:`Payment
+Terminals` section, and tick your terminal's checkbox.
+
+.. image:: terminals/settings-pt.png
+   :alt: checkbox in the settings to enable a payment terminal
+
+Then, follow the corresponding documentation to configure your device:
+
+- :doc:`Adyen configuration <terminals/adyen>`
+- :doc:`Ingenico configuration <terminals/ingenico>`
+- :doc:`SIX configuration <terminals/six>`
+- :doc:`Vantiv configuration <terminals/vantiv>`
+- :doc:`Worldline configuration <terminals/worldline>`
+
+Once the terminal is configured, you can :doc:`create the corresponding payment method and add it to
+the POS <../payment_methods>`.
+
 .. toctree::
    :titlesonly:
 

content/applications/sales/point_of_sale/receipts_invoices.rst

@@ -34,6 +34,8 @@ select the corresponding order and click :guilabel:`Print Receipt`.
    You can filter the list of orders using the search bar. Type in your reference and click
    :guilabel:`Receipt Number`, :guilabel:`Date`, or :guilabel:`Customer`.
 
+.. _receipts-invoices/invoices:
+
 Invoices
 ========
 

content/applications/sales/sales/invoicing/proforma.rst

@@ -1,34 +1,54 @@
-========================
-Send a pro-forma invoice
-========================
+==================
+Pro-forma invoices
+==================
 
-A pro-forma invoice is an abridged or estimated invoice in advance of a
-delivery of goods. It notes the kind and quantity of goods, their value,
-and other important information such as weight and transportation
-charges. Pro-forma invoices are commonly used as preliminary invoices
-with a quotation, or for customs purposes in importation. They differ
-from a normal invoice in not being a demand or request for payment.
+A *pro-forma invoice* is an abridged or estimated invoice sent in advance of a delivery of goods. It
+notes the kind and quantity of goods, their value, and other important information, such as weight
+and transportation charges.
+
+Pro-forma invoices are commonly used as preliminary invoices with a quotation. They are also used
+for customs purposes during importation. They differ from a normal invoice in that they are not a
+demand (or request) for payment.
 
 Activate the feature
 ====================
 
-Go to :menuselection:`SALES --> Configuration --> Settings` and activate
-the *Pro-Forma Invoice* feature.
+In order to utilize pro-forma invoices, the *Pro-Forma Invoice* feature **must** be activated. To do
+that, navigate to :menuselection:`Sales app --> Configuration --> Settings`, and in the
+:guilabel:`Quotations & Orders` section, click the checkbox next to :guilabel:`Pro-Forma Invoice`.
+Then, click :guilabel:`Save` to save all changes.
 
-.. image:: proforma/proforma01.png
-    :align: center
+.. image:: proforma/pro-forma-setting.png
+   :align: center
+   :alt: The Pro-Forma Invoice feature setting in the Odoo Sales application.
 
 Send a pro-forma invoice
 ========================
 
-From any quotation or sales order, you know have an option to send a
-pro-forma invoice.
+With the :guilabel:`Pro-Forma Invoice` feature activated, the option to send a pro-forma invoice is
+now available on any quotation or sales order, via the :guilabel:`Send Pro-Forma Invoice` button.
 
-.. image:: proforma/proforma02.png
-    :align: center
+.. image:: proforma/send-pro-forma-invoice-button.png
+   :align: center
+   :alt: The Send Pro-Forma Invoice button on a typical sales order in Odoo Sales.
 
-When you click on send, Odoo will send an email with the pro-forma
-invoice in attachment.
+When the :guilabel:`Send Pro-Forma Invoice` button is clicked, an email pop-up appears. The
+:guilabel:`Recipients` field is auto-populated with the customer from the sales order or quotation.
+Then, if needed, modify the :guilabel:`Subject` field and the body of the email. The pro-forma
+invoice is automatically added as an attachment to the email.
 
-.. image:: proforma/proforma03.png
-    :align: center
+When ready, click :guilabel:`Send`, and Odoo instantly sends the email, with the attached pro-forma
+invoice, to the customer.
+
+.. image:: proforma/pro-forma-email-message-popup.png
+   :align: center
+   :alt: The email pop-up window that appears with pro-forma invoice attached in Odoo Sales.
+
+.. tip::
+   To preview what the pro-forma invoice looks like, click on the PDF at the bottom of the email
+   pop-up window *before* clicking :guilabel:`Send`. When clicked, the pro-forma invoice is
+   downloaded instantly. Open that PDF to view (and review) the pro-forma invoice.
+
+   .. image:: proforma/pro-forma-pdf.png
+      :align: center
+      :alt: Sample pro-forma invoice PDF from Odoo Sales.

content/developer/reference/cli.rst

@@ -611,6 +611,8 @@ Some conversions don't match the pattern:
 * :option:`--i18n-import` and :option:`--i18n-export` aren't available at all
   from configuration files
 
+.. _reference/cmdline/config_file:
+
 The default configuration file is :file:`{$HOME}/.odoorc` which
 can be overridden using :option:`--config <odoo-bin -c>`. Specifying
 :option:`--save <odoo-bin -s>` will save the current configuration state back

content/legal/terms/i18n/terms_of_sale_fr.rst

@@ -6,7 +6,8 @@ Conditions Générales de Vente
 
 .. only:: html
 
-    `Download PDF <terms_of_sale_fr.pdf>`_
+   `Download PDF <https://www.odoo.com/documentation/{CURRENT_BRANCH}/terms_of_sale_fr.pdf>`_
+
 .. note:: Dernière modification: 20 octobre 2021.
 
 Ces conditions régissent la vente de produits et services entre

content/legal/terms/terms_of_sale.rst

@@ -6,7 +6,7 @@ General Terms of Sale
 
 .. only:: html
 
-   `Download PDF <../../terms_of_sale.pdf>`_
+   `Download PDF <https://www.odoo.com/documentation/{CURRENT_BRANCH}/terms_of_sale.pdf>`_
 
 .. note:: Last revision: October 20, 2021.
 

locale/es/LC_MESSAGES/general.po

@@ -28,6 +28,7 @@
 # Nelson Ramírez <info@konos.cl>, 2023
 # Braulio D. López Vázquez <bdl@odoo.com>, 2023
 # Fernanda Alvarez, 2023
+# Iran Villalobos López, 2023
 # 
 #, fuzzy
 msgid ""
@@ -36,7 +37,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-03-03 11:23+0000\n"
 "PO-Revision-Date: 2021-11-02 08:47+0000\n"
-"Last-Translator: Fernanda Alvarez, 2023\n"
+"Last-Translator: Iran Villalobos López, 2023\n"
 "Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -5311,6 +5312,8 @@ msgstr ""
 #: ../../content/applications/general/users/manage_users.rstNone
 msgid "View of the settings page emphasizing the manage users field in Odoo"
 msgstr ""
+"Vista de la página de ajustes enfatizando el campo de diseño del documento "
+"en Odoo"
 
 #: ../../content/applications/general/users/manage_users.rst:27
 msgid ""
@@ -5333,6 +5336,8 @@ msgstr ""
 #: ../../content/applications/general/users/manage_users.rstNone
 msgid "View of a user’s form emphasizing the access rights tab in Odoo"
 msgstr ""
+"Vista del formulario del usuario enfatizando la pestaña de permisos de "
+"acceso en Odoo. "
 
 #: ../../content/applications/general/users/manage_users.rst:34
 msgid ""
@@ -5350,6 +5355,8 @@ msgid ""
 "View of a user’s form with a notification that the invitation email has been"
 " sent in Odoo"
 msgstr ""
+"Vista del formulario del usuario con una notificación que dice que el correo"
+" de invitación ha sido enviado en Odoo"
 
 #: ../../content/applications/general/users/manage_users.rst:42
 msgid ""
@@ -5373,6 +5380,8 @@ msgid ""
 "View of a user’s form in developer mode emphasizing the user type field in "
 "Odoo"
 msgstr ""
+"Vista del formulario de usuario en el modo desarrollador enfatizando el "
+"campo de tipo de usuario en Odoo"
 
 #: ../../content/applications/general/users/manage_users.rst:53
 msgid ""
@@ -5429,7 +5438,7 @@ msgstr ""
 
 #: ../../content/applications/general/users/manage_users.rstNone
 msgid "Enabling Password Reset in Odoo Settings"
-msgstr ""
+msgstr "Activando el reestablecimiento de contraseñas en los Ajustes de Odoo"
 
 #: ../../content/applications/general/users/manage_users.rst:94
 msgid "Send reset instructions to users"
@@ -5467,6 +5476,8 @@ msgstr ""
 #: ../../content/applications/general/users/manage_users.rstNone
 msgid "Example of an email with a password reset link for an Odoo account"
 msgstr ""
+"Ejemplo de un correo electrónico con un enlace para restablecer la "
+"contraseña para una cuenta de Odoo. "
 
 #: ../../content/applications/general/users/manage_users.rst:114
 msgid "Change users’ passwords"
@@ -5484,7 +5495,7 @@ msgstr ""
 
 #: ../../content/applications/general/users/manage_users.rstNone
 msgid "Change another user's password on Odoo"
-msgstr ""
+msgstr "Cambie la contraseña de otro usuario en Odoo "
 
 #: ../../content/applications/general/users/manage_users.rst:123
 msgid "Enter a new password and confirm by clicking on *Change Password*."
@@ -5540,6 +5551,7 @@ msgstr ""
 #: ../../content/applications/general/users/manage_users.rstNone
 msgid "View of a user’s form emphasizing the multi companies field in Odoo"
 msgstr ""
+"Vista del formulario del usuario enfatizando el campo multiempresas en Odoo"
 
 #: ../../content/applications/general/users/manage_users.rst:152
 msgid ":doc:`companies`"
@@ -6041,7 +6053,7 @@ msgstr "Vaya a :menuselection: `Aplicaciones` e instale el **Módulo VoIP**."
 
 #: ../../content/applications/general/voip/axivox.rstNone
 msgid "VoIP module installation on an Odoo database"
-msgstr ""
+msgstr "Instalación de un módulo VoIP en una base de datos de Odoo"
 
 #: ../../content/applications/general/voip/axivox.rst:24
 msgid ""
@@ -6070,6 +6082,7 @@ msgstr "**Entorno VoIP**: establecido como *Producción*."
 #: ../../content/applications/general/voip/axivox.rstNone
 msgid "Integration of Axivox as VoIP provider in an Odoo database"
 msgstr ""
+"Integración de Axivox como proveedor VoIP en una base de datos de Odoo"
 
 #: ../../content/applications/general/voip/axivox.rst:37
 msgid "Configure the VOIP user in the Odoo's user"
@@ -6098,6 +6111,7 @@ msgstr "**Contraseña SIP**: la *Contraseña SIP* de Axivox"
 #: ../../content/applications/general/voip/axivox.rstNone
 msgid "Integration of Axivox user in the Odoo user preference"
 msgstr ""
+"Integración de un usuario de Axivox en las preferencias de usuario de Odoo "
 
 #: ../../content/applications/general/voip/axivox.rst:50
 msgid ""
@@ -6111,7 +6125,7 @@ msgstr ""
 
 #: ../../content/applications/general/voip/axivox.rst:0
 msgid "SIP credentials in the Axivox manager"
-msgstr ""
+msgstr "Credenciales SIP en el gestor de Axivox"
 
 #: ../../content/applications/general/voip/axivox.rst:58
 msgid "Phone Calls"
@@ -6150,7 +6164,7 @@ msgstr ""
 
 #: ../../content/applications/general/voip/axivox.rst:0
 msgid "\"Missing Parameter\" error message in the Odoo softphone"
-msgstr ""
+msgstr "Mensaje de error \"Parámetro faltante\" en el softphone de Odoo"
 
 #: ../../content/applications/general/voip/axivox.rst:80
 msgid ""
@@ -6166,7 +6180,7 @@ msgstr ""
 
 #: ../../content/applications/general/voip/axivox.rst:0
 msgid "\"Incorrect Number\" error message in the Odoo softphone"
-msgstr ""
+msgstr "Mensaje de error \"Número incorrecto\" en el softphone de Odoo "
 
 #: ../../content/applications/general/voip/onsip.rst:3
 msgid "Use VoIP services in Odoo with OnSIP"

locale/es/LC_MESSAGES/inventory_and_mrp.po

@@ -22,8 +22,8 @@
 # Pablo Rojas <rojaspablo88@gmail.com>, 2023
 # Lucia Pacheco, 2023
 # Braulio D. López Vázquez <bdl@odoo.com>, 2023
-# Iran Villalobos López, 2023
 # Fernanda Alvarez, 2023
+# Iran Villalobos López, 2023
 # 
 #, fuzzy
 msgid ""
@@ -32,7 +32,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-03-03 11:23+0000\n"
 "PO-Revision-Date: 2021-11-02 08:48+0000\n"
-"Last-Translator: Fernanda Alvarez, 2023\n"
+"Last-Translator: Iran Villalobos López, 2023\n"
 "Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -11965,7 +11965,7 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:3
 msgid "Manage vendor bills"
-msgstr ""
+msgstr "Gestionar facturas de proveedor"
 
 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:5
 msgid ""
@@ -12664,7 +12664,7 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rstNone
 msgid "Enable the units of measure option in Odoo Sales"
-msgstr ""
+msgstr "Habilite la opción de unidades de medida en Ventas de Odoo"
 
 #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:29
 msgid "Specify sales and purchase units of measure"
@@ -12724,7 +12724,7 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rstNone
 msgid "Configure a product's units of measure in Odoo"
-msgstr ""
+msgstr "Configure las unidades de medida de un producto en Odoo "
 
 #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:56
 msgid "Create new units of measure and units of measure categories"
@@ -12763,7 +12763,7 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rstNone
 msgid "Create a new units of measure category in Odoo Purchase"
-msgstr ""
+msgstr "Cree una nueva categorría de unidades de medida en Compras de Odoo"
 
 #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:73
 msgid ""
@@ -12798,7 +12798,7 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rstNone
 msgid "Create a new reference unit of measure in Odoo Purchase"
-msgstr ""
+msgstr "Cree una nueva unidad de medida de referencia en Compras de Odoo"
 
 #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:89
 msgid ""
@@ -12855,7 +12855,7 @@ msgstr "Para el rollo de cortina, debe establecer un ratio de 100."
 
 #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rstNone
 msgid "Create a second unit of measure in Odoo Purchase"
-msgstr ""
+msgstr "Cree una segunda unidad de medida en Compras de Odoo"
 
 #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:112
 msgid ""
@@ -12868,3 +12868,5 @@ msgstr ""
 #: ../../content/applications/inventory_and_mrp/purchase/products/uom.rstNone
 msgid "Set a product's units of measure using your own units in Odoo Purchase"
 msgstr ""
+"Establezca una unidad de medida en un producto usando sus propias unidades "
+"en Compras de Odoo"

locale/es/LC_MESSAGES/marketing.po

@@ -12,6 +12,7 @@
 # Martin Trigaux, 2023
 # Braulio D. López Vázquez <bdl@odoo.com>, 2023
 # Fernanda Alvarez, 2023
+# Iran Villalobos López, 2023
 # 
 #, fuzzy
 msgid ""
@@ -20,7 +21,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-03-03 11:23+0000\n"
 "PO-Revision-Date: 2021-11-02 08:49+0000\n"
-"Last-Translator: Fernanda Alvarez, 2023\n"
+"Last-Translator: Iran Villalobos López, 2023\n"
 "Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -2428,15 +2429,15 @@ msgstr "Elija uno de los siguientes :guilabel:`tipos de preguntas`:"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:57
 msgid ":guilabel:`Multiple Lines Text Box`"
-msgstr ""
+msgstr ":guilabel:`Cuadro de texto con múltiples líneas`"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:58
 msgid ":guilabel:`Single Line Text Box`"
-msgstr ""
+msgstr ":guilabel:`Cuadro de texto son una línea`"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:59
 msgid ":guilabel:`Numerical Value`"
-msgstr ""
+msgstr ":guilabel:`Valor númerico`"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:60
 msgid ":guilabel:`Date`"
@@ -2444,19 +2445,19 @@ msgstr ":guilabel:`Fecha`"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:61
 msgid ":guilabel:`Datetime`"
-msgstr ""
+msgstr ":guilabel:`Fecha y hora`"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:62
 msgid ":guilabel:`Multiple choice: only one answer`"
-msgstr ""
+msgstr ":guilabel:`Opción múltiple: solo una respuesta`"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:63
 msgid ":guilabel:`Multiple choice: multiple answers allowed`"
-msgstr ""
+msgstr ":guilabel:`Opción múltiple: se permiten varias respuestas`"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:64
 msgid ":guilabel:`Matrix`"
-msgstr ""
+msgstr ":guilabel:`Matriz`"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:67
 msgid ""
@@ -2465,10 +2466,14 @@ msgid ""
 ":guilabel:`Description` tab always remains the same, regardless of what "
 "question is chosen."
 msgstr ""
+"Aparecerán diferentes funciones en las pestañas :guilabel:`Respuestas` y "
+":guilabel:`Opciones`, dependiendo del :guilabel:`Tipo de pregunta` elegida. "
+"Sin embargo, la pestaña :guilabel:`Descripción` siempre queda igual, sin "
+"importar cual sea la pregunta elegida.      "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:72
 msgid "Create sections and questions"
-msgstr ""
+msgstr "Crear secciones y preguntas"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:74
 msgid ""
@@ -2477,54 +2482,73 @@ msgid ""
 "the :guilabel:`Answers` (if applicable), :guilabel:`Description`, and "
 ":guilabel:`Options` tabs."
 msgstr ""
+"Una vez que seleccionó un  :guilabel:`Tipo de pregunta` hay tres posibles "
+"pestañas donde puede personalizar la información para la pregunta. Estas "
+"incluyen las pestañas de guilabel:`Respuestas` (si aplica), "
+":guilabel:`Descripción` y :guilabel:`Opciones`.   "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:78
 msgid ""
 "Each tab offers a variety of different features depending on what "
 ":guilabel:`Question Type` was chosen."
 msgstr ""
+"Cada pestaña ofrece una variedad diferentes de funciones dependiendo de qué "
+":guilabel:`Tipo de pregunta` escogió.  "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:81
 msgid ""
 "For example, in the :guilabel:`Options` tab, the following options may "
 "appear:"
 msgstr ""
+"Por ejemplo, en la pestaña de :guilabel:`Opciones`, pueden aparecer las "
+"siguientes opciones: "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:83
 msgid ":guilabel:`Mandatory Answer`: the question must be answered."
-msgstr ""
+msgstr ":guilabel:`Respuesta obligatoria`: debe responder la pregunta."
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:84
 msgid ""
 ":guilabel:`Matrix Type`: for matrix-type questions, select if one choice or "
 "multiple choices can be selected per row."
 msgstr ""
+":guilabel:`Tipo de matriz`: para preguntas de tipo matriz, seleccione si se "
+"puede seleccionar una o más opciones por fila. "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:86
 msgid ":guilabel:`Number of columns`: select how many columns are displayed."
 msgstr ""
+":guilabel:`Número de caolumnas`: seleccione cuántas columnas se muestran."
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:87
 msgid ":guilabel:`Images on answers`: allow images on the answer options."
 msgstr ""
+":guilabel:`Imágenes en las respuestas`: permita las imágenes en las opciones"
+" de respuesta."
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:88
 msgid ""
 ":guilabel:`Conditional Display`: determine if the question is displayed "
 "based on the participant's answer to a previous question."
 msgstr ""
+":guilabel:`Mostrar con condición`: determina si la pregunta se muestra con "
+"base en la respuesta del participante de una pregunta previa. "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:90
 msgid ""
 ":guilabel:`Show Comments Field`: allow the participant to type a comment in "
 "a text box."
 msgstr ""
+":guilabel:`Mostrar campo de comentarios`: permita al participante escribir "
+"un comentario en un cuadro de texto. "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:91
 msgid ""
 ":guilabel:`Question Time Limit`: for live session surveys, set a time limit "
 "for the question."
 msgstr ""
+":guilabel:`Tiempo límite de la pregunta`: para las encuestas en sesiones en "
+"vivo, establezca un tiempo límite para la pregunta."
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:94
 msgid "Conditional Display"
@@ -2535,6 +2559,9 @@ msgid ""
 ":guilabel:`Conditional Display` means the question is only displayed if the "
 "specified conditional answer has been selected in a previous question."
 msgstr ""
+":guilabel:`Visualización condicionada` significa que la pregunta solo es "
+"visible si  se seleccionó la respuesta condicional específica en la pregunta"
+" anterior. "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:99
 msgid ""
@@ -2542,12 +2569,19 @@ msgid ""
 ":guilabel:`Triggering Question` field appears. Select a question from the "
 "survey."
 msgstr ""
+"Cuando está seleccionada la casilla que está junto a "
+":guilabel:`Visualización condicional`, aparecerá el campo de "
+":guilabel:`Respuesta desencadenante`. Seleccione una pregunta de la "
+"encuesta. "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:102
 msgid ""
 "Then, a :guilabel:`Triggering Answer` field appears. Here, select which "
 "answer will trigger this :guilabel:`Conditional Display` question."
 msgstr ""
+"Luego, aparecerá un campo de :guilabel:`Respuesta desencadenante`. "
+"Seleccione que respuesta desencadenará la pregunta configurada como "
+":guilabel:`Visualización condicional`."
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:106
 msgid "Options tab"
@@ -2558,29 +2592,34 @@ msgid ""
 "Back on the main survey template form, under the :guilabel:`Options` tab, "
 "there are different sections of settings that can be modified."
 msgstr ""
+"En la plantilla del formulario de la encuesta principal, en la pestaña "
+":guilabel:`Opciones`, hay secciones de ajustes que puede modificar.  "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:111
 msgid "The sections include:"
-msgstr ""
+msgstr "Estas secciones incluyen: "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:113
 msgid ""
 ":guilabel:`Questions`: focuses on the overall presentation of the survey"
 msgstr ""
+":guilabel:`Preguntas`: se enfoca en la presentación general de la encuesta"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:114
 msgid ":guilabel:`Scoring`: decides how the survey is scored"
-msgstr ""
+msgstr ":guilabel:`Puntaje`: establece como se califica la encuesta "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:115
 msgid ":guilabel:`Candidates`: manages access to the survey"
-msgstr ""
+msgstr ":guilabel:`Candidatos`: gestiona el acceso a la encuesta "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:116
 msgid ""
 ":guilabel:`Live Session`: enables the survey into a real-time group "
 "activity."
 msgstr ""
+":guilabel:`Sesión en vivo`: convierte la encuesta en una actividad grupal en"
+" tiempo real. "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:119
 msgid "Questions"
@@ -2591,18 +2630,20 @@ msgid ""
 "First, select the :guilabel:`Layout` of the survey. The following options "
 "can be chosen:"
 msgstr ""
+"Primero, seleccione el :guilabel:`Diseño` de la encuesta. Puede elegir de "
+"entre las siguientes opciones: "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:123
 msgid ":guilabel:`One page with all the questions`"
-msgstr ""
+msgstr ":guilabel:`Una página con todas las preguntas`"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:124
 msgid ":guilabel:`One page per section`"
-msgstr ""
+msgstr ":guilabel:`Una página por sección`"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:125
 msgid ":guilabel:`One page per question`"
-msgstr ""
+msgstr ":guilabel:`Una página por pregunta`"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:127
 msgid ""
@@ -2611,6 +2652,10 @@ msgid ""
 "appears. If selected, the :guilabel:`Back Button` option allows the "
 "participant to go back to a question during the survey."
 msgstr ""
+"Si selecciona la opción :guilabel:`Una página por sección` o :guilabel:`Una "
+"página por pregunta`, aparecerá la opción :guilabel:`Botón de retroceso`. Si"
+" selecciona la opción de :guilabel:`Botón de retroceso`, el participante "
+"podrá regresar a una pregunta mientras hace la encuesta.   "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:131
 msgid ""
@@ -2619,6 +2664,10 @@ msgid ""
 " displayed. It is shown as either a :guilabel:`Percentage` or a "
 ":guilabel:`Number`."
 msgstr ""
+"Entre las opciones de :guilabel:`Diseño` se encuentra el ajuste de "
+":guilabel:`Modo Progreso`, que indica cómo se muestra el progreso del "
+"participante. Se muestra como un  :guilabel:`Percentaje` o un "
+":guilabel:`Número`.  "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:135
 msgid ""
@@ -2626,6 +2675,10 @@ msgid ""
 "To implement this option, simply check the box, and enter the amount of time"
 " (in minutes) participants have to complete the survey."
 msgstr ""
+"Después, hay una opción disponible para agregar un :guilabel:`Tiempo límite "
+"de la encuesta`. Para activar esta opción, simplemente seleccione la casilla"
+" e introduzca la cantidad de tiempo (en minutos) que tienen los "
+"participantes para terminar la encuesta.  "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:139
 msgid ""
@@ -2634,6 +2687,11 @@ msgid ""
 "section`, in other words, the number of random questions can be configured "
 "by section. This mode is ignored in a live session."
 msgstr ""
+"Después de la opción :guilabel:`Tiempo límite de la encuesta` hay una "
+"sección llamada :guilabel:`Selección de preguntas`. Aquí, puede seleccionar "
+"que las preguntas aparezcan :guilabel:`Aleatorio por sección`, es decir, "
+"puede configurar el número de preguntas aleatorias por sección. Esta opción "
+"no se toma en cuenta en las sesiones en vivo.      "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:144
 #: ../../content/applications/marketing/surveys/overview/scoring.rst:56
@@ -2649,18 +2707,20 @@ msgid ""
 "The following options are available when deciding how a :guilabel:`Scoring` "
 "method:"
 msgstr ""
+"Al decidir un método de :guilabel:`Puntuación` podrá escoger de entre las "
+"siguientes opciones:   "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:151
 msgid ":guilabel:`No scoring`"
-msgstr ""
+msgstr ":guilabel:`Sin puntaje`"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:152
 msgid ":guilabel:`Scoring with answers at the end`"
-msgstr ""
+msgstr ":guilabel:`Puntaje con respuestas al final`"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:153
 msgid ":guilabel:`Scoring without answers at the end`"
-msgstr ""
+msgstr ":guilabel:`Puntaje sin respuestas al final`"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:155
 msgid ""
@@ -2669,6 +2729,10 @@ msgid ""
 ":guilabel:`Success %` field appears. Set the percentage of correct answers "
 "needed to pass the survey."
 msgstr ""
+"Si selecciona la opción :guilabel:`Puntaje con respuestas al final` o "
+":guilabel:`Puntaje din respuestas al final`, aparecerá un campo de "
+":guilabel:`Porcentaje de puntaje obligatorio`. Establezca el puntaje de "
+"respuestas correctas necesarias para aprobar la encuesta.    "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:159
 msgid ""
@@ -2680,6 +2744,13 @@ msgid ""
 "score, an email from Odoo will automatically be sent to that person using "
 "the selected email template."
 msgstr ""
+"Luego, tendrá la opción de convertir la encuesta en una certificación. Para "
+"hacerlo, seleccione la casilla que está junto a la opción :guilabel:`Es una "
+"certificación` y aparecerán otros dos campos. Seleccione un color en el "
+"campo :guilabel:`Plantilla de la certificación` y luego elija una "
+":guilabel:`Plantilla de correo electrónico`. Cuando un participante aprueba "
+"la certificación con el puntaje requerido, se le enviará automáticamente un "
+"correo usando la plantilla seleccionada.       "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:165
 msgid ""
@@ -2687,6 +2758,9 @@ msgid ""
 ":guilabel:`Certification Badge` is set, the survey participant also receives"
 " a badge upon passing the certification."
 msgstr ""
+"Si la función :guilabel:`Dar insignia` está activada y está establecida la "
+"opción :guilabel:`Insignia de certificación`, el participante también "
+"recibirá una insignia al aprobar la certificación. "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:169
 #: ../../content/applications/marketing/surveys/overview/time_random.rst:48
@@ -2703,6 +2777,9 @@ msgid ""
 "options to choose between: :guilabel:`Anyone with the link` and "
 ":guilabel:`Invited people only`."
 msgstr ""
+"Para determinar el acceso a la encuesta, el :guilabel:`Modo de acceso` le "
+"permite escoger de entre dos opciones: :guilabel:`Cualquier persona que "
+"tenga el enlace` y :guilabel:`Solo personas con invitación`. "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:177
 msgid ""
@@ -2712,6 +2789,12 @@ msgid ""
 "also populates, in which the number of survey attempts is defined for the "
 "participant."
 msgstr ""
+"Debajo de la casilla :guilabel:`Evaluación solo para gerentes`, está la "
+"opción de :guilabel:`Se requiere inicio de sesión` para solicitarle al "
+"participante que inicie sesión para realizar la encuesta. Si está activada "
+"esta opción, también se completará un campo de  :guilabel:`Limitar "
+"intentos`, en el cual se definen el número de intentos que tiene el "
+"participante para realizar la encuesta. "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:182
 msgid "Live Session"
@@ -2723,6 +2806,9 @@ msgid ""
 "conducting surveys in real-time, wherein they directly engage with and "
 "collect answers from a live audience."
 msgstr ""
+"La sección :guilabel:`Sesión en vivo` está dedicada a los usuarios que "
+"realizan encuestas en tiempo real, donde interactúan y obtienen respuestas "
+"de una audiencia en vivo. "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:187
 msgid ""
@@ -2732,10 +2818,15 @@ msgid ""
 "answers`. By checking it, attendees will get more points if they answer "
 "quickly."
 msgstr ""
+"Personalice el :guilabel:`Código de sesión` aquí; los participantes "
+"necesitan este código para acceder a la encuesta de la sesión en vivo. "
+"Premie a los participantes cuando repondan rápidamente seleccionando la "
+"casilla :guilabel:`Premiar respuestas rápidas`. Al seleccionarla, los "
+"asistentes obtendrán más puntos si responden rápidamente. "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:193
 msgid "Description tab"
-msgstr ""
+msgstr "Pestaña de descripción"
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:195
 msgid ""
@@ -2744,6 +2835,11 @@ msgid ""
 "beneath the title on the survey's homepage, which is on the front end of the"
 " website made through the Odoo :guilabel:`Website` app."
 msgstr ""
+"En la página principal de la plantilla de la encuesta está la pestaña de "
+":guilabel:`Descripción`, dónde puede agregar una descripción personalizada "
+"de la encuesta. Esto se muestra debajo del título de la página principal de "
+"la encuesta, que está en el frontend de la página web que creó a través de "
+"la aplicación :guilabel:`Sitio web` de Odoo.    "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:200
 msgid "Test and share the survey"
@@ -2755,6 +2851,10 @@ msgid ""
 "errors before finally sending it out to the participants by clicking "
 ":guilabel:`Test` in the upper left corner of the survey template page."
 msgstr ""
+"Una vez que creó y guardó la encuesta, haga una prueba para verificar que no"
+" haya errores antes de enviarla a los participantes haciendo clic en el "
+"botón :guilabel:`Prueba` que está en la esquina superior izquierda de la "
+"página de la plantilla de la encuesta.  "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:206
 msgid ""
@@ -2763,6 +2863,10 @@ msgid ""
 " participants. Proceed to run through the survey, like a normal participant,"
 " to check for errors."
 msgstr ""
+"Al activar está función, Odoo lo redirecciona a una versión de prueba de la "
+"encuesta en el frontend del sitio web. Esta página muestra como lucirá la "
+"encuesta para los participantes. Realice la encuesta como lo haría el "
+"participante para revisar que no haya errores. "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:210
 msgid ""
@@ -2772,6 +2876,12 @@ msgid ""
 " the backend, make any further changes, as needed, before officially sending"
 " the survey out to participants."
 msgstr ""
+"Para regresar al formulario de la plantilla de la encuesta en el backend, "
+"solo haga clic en el enlace que está en el panel azul en la parte superior "
+"de la página que dice :guilabel:`Está es una prueba. Editar encuesta`. Una "
+"vez que Odoo lo redirecciona a la plantilla de la encuesta en el backend, "
+"haga los cambios necesarios antes de enviar oficialmente la encuesta a los "
+"participantes. "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:215
 msgid ""
@@ -2779,6 +2889,10 @@ msgid ""
 ":guilabel:`Start Survey` button in the upper-left corner of the survey "
 "template form. Then, click :guilabel:`Share`."
 msgstr ""
+"Cuando esté listo para compartir la encuesta con la audiencia, haga clic en "
+"el botón :guilabel:`Iniciar encuesta` que está en el lado superior izquierdo"
+" del formulario de la plantilla de la encuesta. Luego haga clic en  "
+":guilabel:`Compartir`. "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:218
 msgid ""
@@ -2787,6 +2901,12 @@ msgid ""
 " the :guilabel:`Additional emails` field (for contacts that do not want to "
 "be listed in the Odoo database). Finally, click :guilabel:`Send`."
 msgstr ""
+"En la ventana emergente que aparece, en el campo :guilabel:`Destinatarios`, "
+"agregue a los destinatarios que recibirán la encuesta (para contactos ya "
+"existentes en la base de datos de Odoo). También puede elegir el campo "
+":guilabel:`Correos adicionales` (para contactos que no quieran estar "
+"registrados en la base de datos de Odoo). Finalmente, haga clic en "
+":guilabel:`Enviar`.  "
 
 #: ../../content/applications/marketing/surveys/overview/create.rst:222
 msgid ""
@@ -2795,10 +2915,15 @@ msgid ""
 "button in the upper left corner. To end the survey, click the "
 ":guilabel:`Close` button on the survey template form."
 msgstr ""
+"Mientras recibe las respuestas, revíselas haciendo clic en el botón "
+"inteligente de :guilabel:`Respuestas` en el formulario de la plantilla de la"
+" encuesta o en el botón de :guilabel:`Ver resultados` que está en la esquina"
+" superior izquierda. Para terminar la encuesta, haga clic en el botón de "
+":guilabel:`Cerrar` en el formulario de la plantilla de la encuesta.  "
 
 #: ../../content/applications/marketing/surveys/overview/scoring.rst:3
 msgid "Scoring surveys"
-msgstr ""
+msgstr "Puntaje de las encuestas"
 
 #: ../../content/applications/marketing/surveys/overview/scoring.rst:5
 msgid ""
@@ -2807,6 +2932,10 @@ msgid ""
 "survey, these points are summed up, resulting in the participant's final "
 "score."
 msgstr ""
+"Para tener una métrica del rendimiento, conocimiento y satisfacción general "
+"del participante, Odoo asigna puntos a las respuestas de las encuestas. Al "
+"final de la encuesta, estos puntos se suman dando como resultado el puntaje "
+"final.  "
 
 #: ../../content/applications/marketing/surveys/overview/scoring.rst:9
 msgid ""
@@ -2815,6 +2944,11 @@ msgid ""
 "Under the :guilabel;`Scoring` section, choose between :guilabel:`Scoring "
 "with answers at the end` or :guilabel:`Scoring without answers at the end`."
 msgstr ""
+"Para agregar puntos a las encuestas, abra la aplicación "
+":guilabel:`Encuestas`, seleccione el formulario de encuesta que desee y haga"
+" clic en la pestaña de :guilabel:`Opciones`. En la sección "
+":guilabel;`Puntaje`, seleccione entre las opciones de :guilabel:`Puntaje con"
+" respuestas al final` o :guilabel:`Puntaje sin respuestas al final`.    "
 
 #: ../../content/applications/marketing/surveys/overview/scoring.rst:14
 msgid ""
@@ -2823,6 +2957,10 @@ msgid ""
 " got right or wrong. On questions where there was an incorrect answer, the "
 "correct answer will be highlighted."
 msgstr ""
+":guilabel:`Puntaje con respuestas al final` le muestra al participante sus "
+"respuestas correctas e incorrectas después de haber terminado la encuesta. "
+"En las preguntas donde respondió incorrectamente, la respuesta correcta "
+"estará resaltada. "
 
 #: ../../content/applications/marketing/surveys/overview/scoring.rst:18
 msgid ""
@@ -2830,6 +2968,9 @@ msgid ""
 "participant their answer choices after completing the survey, only their "
 "final score."
 msgstr ""
+":guilabel:`Puntaje sin respuestas al final` no le muestra al participante "
+"sus respuestas después de terminar la encuesta, solo aparece su puntaje "
+"final. "
 
 #: ../../content/applications/marketing/surveys/overview/scoring.rst:21
 msgid ""
@@ -2838,6 +2979,10 @@ msgid ""
 "answer` box for the choice that is the correct answer and attach a score "
 "value."
 msgstr ""
+"Para indicar cuáles son las respuestas correctas, haga clic en la  "
+":guilabel:`Pestaña de preguntas` y elija una pregunta. En el formulario de "
+"preguntas, seleccione la casilla  :guilabel:`Respuesta correcta` para la "
+"opción correcta y agregue un valor de puntuación. "
 
 #: ../../content/applications/marketing/surveys/overview/scoring.rst:25
 msgid ""
@@ -2845,6 +2990,10 @@ msgid ""
 ":guilabel:`Success %`. The percentage entered determines what percentage of "
 "correct answers is needed to pass the survey."
 msgstr ""
+"En la pestaña :guilabel:`Opciones` de la encuesta, establezca el "
+":guilabel:`Porcentaje del puntaje obligatorio`. El porcentaje que introduzca"
+" determina el porcentaje correcto de respuestas correctas para aprobar la "
+"encuesta.    "
 
 #: ../../content/applications/marketing/surveys/overview/scoring.rst:28
 msgid ""
@@ -2853,6 +3002,11 @@ msgid ""
 "indicates that the survey asks questions to test the participants' knowledge"
 " level on a subject."
 msgstr ""
+"Más adelante en la pestaña de :guilabel:`Opciones` de la encuesta, los "
+"administradores de la misma también pueden convertir la encuesta en una "
+"certificación. Una certificación indica que la encuesta contiene preguntas "
+"que ponen a prueba el nivel de conocimiento del participante sobre un tema."
+"  "
 
 #: ../../content/applications/marketing/surveys/overview/scoring.rst:32
 msgid ""
@@ -2862,6 +3016,12 @@ msgid ""
 "survey with a final score that is greater than or equal to the set "
 ":guilabel:`Success %`."
 msgstr ""
+"Al activar la opción de  :guilabel:`Es una certificación`, seleccione "
+"también una :guilabel:`Plantilla de correo electrónico de la certificación`."
+" Se enviará automáticamente la certificación usando esa plantilla de correo "
+"a los usuarios que aprobaron la encuesta con un puntaje final que sea mayor "
+"o igual al que estableció en :guilabel:`Porcentaje de puntuación "
+"obligatorio`.    "
 
 #: ../../content/applications/marketing/surveys/overview/scoring.rst:36
 msgid ""
@@ -2872,12 +3032,21 @@ msgid ""
 "option to :guilabel:`Give Badge`, located beneath the "
 ":guilabel:`Certification` options in the :guilabel:`Scoring` section."
 msgstr ""
+"En la sección de :guilabel:`Participantes`, puede pedirle a los "
+"participantes que inicien sesión para realizar la encuesta. Si está activada"
+" la opción de :guilabel:`Se requiere inicio de sesión`, aparecerán dos "
+"nuevas opciones: la casilla de :guilabel:`Límitar intentos`, lo que limíta "
+"el número de veces que un participante puede intentar realizar la encuesta, "
+"y la opción :guilabel:`Dar insignia`, ubicada debajo de las opciones de "
+":guilabel:`Certificación` en la sección de :guilabel:`Puntaje. `   "
 
 #: ../../content/applications/marketing/surveys/overview/scoring.rstNone
 msgid ""
 "Setting the Required Score (percentage), login required, and certification "
 "template."
 msgstr ""
+"Configuración del puntaje requerido (en porcentaje), el inicio de sesión "
+"requerido y la plantilla de la certificación. "
 
 #: ../../content/applications/marketing/surveys/overview/scoring.rst:46
 msgid ""
@@ -2886,24 +3055,33 @@ msgid ""
 "gaining points. Besides the awardee, website visitors who access the "
 ":guilabel:`Courses` page will also be able to see the granted badges."
 msgstr ""
+"Las insignias se muestran en la sección de eLearning del portal del usuario "
+"y son una forma de establecer objetivos y premiar a los participantes por "
+"aprobar las encuestas o ganar puntos. Además del participante premiado, los "
+"visitantes del sitio web que accedan a la página de :guilabel:`Cursos` "
+"también podrán ver las insignias,"
 
 #: ../../content/applications/marketing/surveys/overview/scoring.rstNone
 msgid "Example of how a badge looks on the eLearning portion of the website."
 msgstr ""
+"Ejemplo de cómo se ve una insignia en la sección de eLearning del sitio web."
+" "
 
 #: ../../content/applications/marketing/surveys/overview/time_random.rst:3
 msgid "Timed and randomized questions"
-msgstr ""
+msgstr "Preguntas cronometradas y aleatorias "
 
 #: ../../content/applications/marketing/surveys/overview/time_random.rst:5
 msgid ""
 "When creating a survey in Odoo, there are options to set a time limit on the"
 " survey and randomize the questions."
 msgstr ""
+"Al crear una encuesta en Odoo, hay opciones que le permiten establecer un "
+"tiempo límite en la encuesta y mostrar las preguntas aleatoriamente. "
 
 #: ../../content/applications/marketing/surveys/overview/time_random.rst:9
 msgid "Time limit"
-msgstr ""
+msgstr "Tiempo límite"
 
 #: ../../content/applications/marketing/surveys/overview/time_random.rst:11
 msgid ""
@@ -2913,16 +3091,26 @@ msgid ""
 " external resources (e.g. web search), and reduces the survey to a \"closed "
 "book\" testing environment."
 msgstr ""
+"Durante una encuesta con tiempo límite, los participantes deben terminarla "
+"dentro de un periodo de tiempo establecido. Un caso de uso muy común en el "
+"que se usa el tiempo límite es para reducir la propabilidad de que el "
+"participante busque las respuestas en otro lado (por ejemplo, en internet), "
+"y establce la encuesta como un ambiente de prueba a \"libro cerrado\". "
 
 #: ../../content/applications/marketing/surveys/overview/time_random.rst:16
 msgid ""
 "Find the :guilabel:`Survey Time Limit` setting in the :guilabel:`Options` "
 "tab of the survey form, under the :guilabel:`Questions` section."
 msgstr ""
+"Busque la opción :guilabel:`Tiempo límite de la encuesta` en la pestaña de "
+":guilabel:`Opciones` del formulario de la encuesta, en la sección de  "
+":guilabel:`Preguntas`.      "
 
 #: ../../content/applications/marketing/surveys/overview/time_random.rstNone
 msgid "Time limit field in the options tab of a survey template form."
 msgstr ""
+"El campo de tiempo límite en la pestaña de opciones de una plantilla del "
+"formulario de una encuesta. "
 
 #: ../../content/applications/marketing/surveys/overview/time_random.rst:23
 msgid ""
@@ -2930,16 +3118,22 @@ msgid ""
 "displayed on every page of the survey, letting participants keep track of "
 "the time remaining while the survey is active."
 msgstr ""
+"Cuando selecciona la opción  :guilabel:`Tiempo límite de la encuesta`, "
+"aparecerá un cronómetro en cada página de la encuesta, permitiendole a los "
+"participantes estar atentos al tiempo restante mientras la encuesta está "
+"activa.  "
 
 #: ../../content/applications/marketing/surveys/overview/time_random.rst:27
 msgid ""
 "Participants that do not submit their survey by the preconfigured time limit"
 " will *not* have their answers saved."
 msgstr ""
+"A los participantes que no suban su encuesta en el tiempo límite "
+"preesablecido *no* se les guardarán sus respuestas. "
 
 #: ../../content/applications/marketing/surveys/overview/time_random.rst:31
 msgid "Randomized selection"
-msgstr ""
+msgstr "Aleatorio por sección "
 
 #: ../../content/applications/marketing/surveys/overview/time_random.rst:33
 msgid ""
@@ -2948,6 +3142,11 @@ msgid ""
 "randomization as a survey method discourages participants from looking at "
 "each other's responses, and helps control for individual testing."
 msgstr ""
+"Cuando una encuesta es aleatoria, Odoo mezcla las preguntas y las muestra en"
+" un orden aleatorio cada vez que un participante comienza a responder las "
+"preguntas. Utilizar este método no le permite a los participantes comparar "
+"sus respuestas entre ellos y ayuda a darle control para pruebas "
+"individuales. "
 
 #: ../../content/applications/marketing/surveys/overview/time_random.rst:37
 msgid ""
@@ -2958,7 +3157,13 @@ msgid ""
 "count` column. From there, determine how many questions (per section) Odoo "
 "should select and display during the shuffling of questions."
 msgstr ""
+"Para hacer aleatoria una encuesta, haga clic en la pestaña de "
+":guilabel:`Opciones` en el formulario de la encuesta. En la sección de "
+":guilabel:`Preguntas`, seleccione :guilabel:`Aleatorio por sección` para el "
+"campo de :guilabel:`Selección de preguntas`. Después de activarla, vaya a la"
+" pestaña de :guilabel:``      "
 
 #: ../../content/applications/marketing/surveys/overview/time_random.rstNone
 msgid "Randomized question count in the questions tab of a survey."
 msgstr ""
+"Número de preguntas aleatorias en la pestaña de preguntas de una encuesta. "

locale/es/LC_MESSAGES/productivity.po

@@ -14,6 +14,7 @@
 # Pedro M. Baeza <pedro.baeza@tecnativa.com>, 2023
 # Braulio D. López Vázquez <bdl@odoo.com>, 2023
 # Fernanda Alvarez, 2023
+# Iran Villalobos López, 2023
 # 
 #, fuzzy
 msgid ""
@@ -22,7 +23,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-03-03 11:23+0000\n"
 "PO-Revision-Date: 2021-11-02 08:49+0000\n"
-"Last-Translator: Fernanda Alvarez, 2023\n"
+"Last-Translator: Iran Villalobos López, 2023\n"
 "Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -4654,10 +4655,12 @@ msgid ""
 "With Studio, you can edit existing PDF reports (e.g., orders and quotations)"
 " or create new ones."
 msgstr ""
+"Con Studio, puede editar reportes en PDF existentes (por ejemplo, órdenes y "
+"cotizaciones) o crear nuevos. "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:10
 msgid "Default layout"
-msgstr ""
+msgstr "Diseño predeterminado "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:12
 msgid ""
@@ -4666,12 +4669,18 @@ msgid ""
 "Document Layout`. Layout settings apply to all reports but only to the "
 "current company."
 msgstr ""
+"El diseño predeterminado de los reportes se maneja fuera de Studio. Vaya a "
+":menuselection:`Ajustes --> Empresas: Diseño del documento --> Configruación"
+" del diseño del documento`. Los ajustes del diseño aplican a todos los "
+"reportes pero solo de la empresa actual. "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:17
 msgid ""
 "Use :guilabel:`Download PDF Preview` to view how the different settings "
 "affect the layout of a sample invoice."
 msgstr ""
+"Use :guilabel:`Descargar la vista previa del PDF` para ver como los "
+"diferentes ajustes pueden alterar el diseño de una simple factura. "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:23
 msgid "Layout"
@@ -4679,7 +4688,7 @@ msgstr "Diseño"
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:25
 msgid "Four layouts are available."
-msgstr ""
+msgstr "Hay cuatro diseños disponibles. "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:29
 msgid "Light"
@@ -4687,7 +4696,7 @@ msgstr "Light"
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:0
 msgid "Light report layout sample"
-msgstr ""
+msgstr "Ejemplo del diseño de reporte Light"
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:35
 msgid "Boxed"
@@ -4695,7 +4704,7 @@ msgstr "Archivado"
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:0
 msgid "Boxed report layout sample"
-msgstr ""
+msgstr "Ejemplo del diseño de reporte Con tabla "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:41
 msgid "Bold"
@@ -4703,7 +4712,7 @@ msgstr "Negrita"
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:0
 msgid "Bold report layout sample"
-msgstr ""
+msgstr "Ejemplo del diseño del reporte en Negritas"
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:47
 msgid "Striped"
@@ -4711,7 +4720,7 @@ msgstr "Listado"
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:0
 msgid "Striped report layout sample"
-msgstr ""
+msgstr "Ejemplo del diseño de reporte Subrayado"
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:56
 msgid "Font"
@@ -4722,47 +4731,53 @@ msgid ""
 "Seven fonts are available. Click on the links below to preview them on "
 "`Google Fonts <https://fonts.google.com/>`_."
 msgstr ""
+"Están disponibles siete tipos de letra. Haga clic en los enlaces a "
+"continuación para obtener una vista previa en `Google Fonts "
+"<https://fonts.google.com/>`_. "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:61
 msgid "`Lato <https://fonts.google.com/specimen/Lato#type-tester>`_"
-msgstr ""
+msgstr "`Lato <https://fonts.google.com/specimen/Lato#type-tester>`_"
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:62
 msgid "`Roboto <https://fonts.google.com/specimen/Roboto#type-tester>`_"
-msgstr ""
+msgstr "`Roboto <https://fonts.google.com/specimen/Roboto#type-tester>`_"
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:63
 msgid "`Open Sans <https://fonts.google.com/specimen/Open+Sans#type-tester>`_"
 msgstr ""
+"`Open Sans <https://fonts.google.com/specimen/Open+Sans#type-tester>`_"
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:64
 msgid ""
 "`Montserrat <https://fonts.google.com/specimen/Montserrat#type-tester>`_"
 msgstr ""
+"`Montserrat <https://fonts.google.com/specimen/Montserrat#type-tester>`_"
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:65
 msgid "`Oswald <https://fonts.google.com/specimen/Oswald#type-tester>`_"
-msgstr ""
+msgstr "`Oswald <https://fonts.google.com/specimen/Oswald#type-tester>`_"
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:66
 msgid "`Raleway <https://fonts.google.com/specimen/Raleway#type-tester>`_"
-msgstr ""
+msgstr "`Raleway <https://fonts.google.com/specimen/Raleway#type-tester>`_"
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:67
 msgid "`Tajawal <https://fonts.google.com/specimen/Tajawal#type-tester>`_"
-msgstr ""
+msgstr "`Tajawal <https://fonts.google.com/specimen/Tajawal#type-tester>`_"
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:70
 msgid ":guilabel:`Tajawal` supports both Arabic and Latin scripts."
-msgstr ""
+msgstr ":guilabel:`Tajawal` supports both Arabic and Latin scripts."
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:75
 msgid "Company logo"
-msgstr ""
+msgstr "Logo de la empresa "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:77
 msgid "Upload an image file to add a :guilabel:`Company Logo`."
 msgstr ""
+"Suba un archivo de imagen para agregar un :guilabel:`Logo de la empresa`. "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:80
 msgid ""
@@ -4770,6 +4785,9 @@ msgid ""
 " can access by going to :menuselection:`General Settings --> Companies --> "
 "Update Info`."
 msgstr ""
+"Esto agrega el logo al registro de la empresa en el modelo *Empresa*, al que"
+" puede acceder si va a :menuselection:`Ajustes generales --> Empresas --> "
+"Actualizar información`."
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:86
 msgid "Colors"
@@ -4781,32 +4799,39 @@ msgid ""
 " important elements. The default colors are automatically generated based on"
 " the colors of the logo."
 msgstr ""
+"Cambie los colores primarios y secundarios que usa en los reportes para "
+"resaltar elementos importantes. Los colores predeterminados se generan "
+"automáticamente con base en los colores del logo. "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:94
 msgid "Layout background"
-msgstr ""
+msgstr "Diseño del fondo "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:96
 msgid "Change the :guilabel:`Layout Background` of the report:"
-msgstr ""
+msgstr "Cambie el :guilabel:`Diseño del fondo` del reporte: "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:98
 msgid ":guilabel:`Blank`: nothing is displayed."
-msgstr ""
+msgstr ":guilabel:`En blanco`: no se muestra nada."
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:99
 msgid ""
 ":guilabel:`Geometric`: an image featuring geometric shapes is displayed in "
 "the background."
 msgstr ""
+":guilabel:`Geometrico`: se muestra una imagen con figuras geométricas de "
+"fondo. "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:100
 msgid ":guilabel:`Custom`: use a custom background image by uploading one."
 msgstr ""
+":guilabel:`Personalizado`: suba una imagen personalizada para usarla de "
+"fondo."
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:105
 msgid "Company tagline"
-msgstr ""
+msgstr "Lema de la empresa"
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:107
 msgid ""
@@ -4814,10 +4839,13 @@ msgid ""
 " reports <studio/pdf-reports/header-footer/external>`. You can add multiple "
 "lines of text."
 msgstr ""
+"El :guilabel:`Lema de la empresa` se muestra en el encabezado de "
+":ref:`Reportes externos <studio/pdf-reports/header-footer/external>`. Puede "
+"agregar varias líneas de texto.  "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:113
 msgid "Company details"
-msgstr ""
+msgstr "Detalles de la empresa "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:115
 msgid ""
@@ -4825,6 +4853,9 @@ msgid ""
 ":ref:`External reports <studio/pdf-reports/header-footer/external>`. You can"
 " add multiple lines of text."
 msgstr ""
+"Los :guilabel:`Detalles de la empresa` se muestran en el encabezado de "
+":ref:`Reportes externos <studio/pdf-reports/header-footer/external>`. Puede "
+"agregar varias líneas de texto.    "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:121
 msgid "Footer"
@@ -4836,6 +4867,9 @@ msgid ""
 "reports' <studio/pdf-reports/header-footer/external>` footers. You can add "
 "multiple lines of text."
 msgstr ""
+"Use el campo :guilabel:`Pie de página` para poner texto en el pie de página "
+"de los :ref:`Reportes externos' <studio/pdf-reports/header-"
+"footer/external>`. Puede agrergar varias líneas de texto. "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:129
 msgid "Paper format"
@@ -4847,6 +4881,9 @@ msgid ""
 "You can either select :guilabel:`A4` (21 cm x 29.7 cm) or :guilabel:`US "
 "Letter` (21.59 cm x 27.54 cm)."
 msgstr ""
+"Use el campo de :guilabel:`Formato de papel` para cambiar el tamaño del "
+"papel de los repórtes. Puede seleccionar :guilabel:`A4` (21 cm x 29.7 cm) o "
+":guilabel:`Carta US` (21.59 cm x 27.54 cm)."
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:135
 msgid ""
@@ -4858,10 +4895,12 @@ msgstr ""
 #: ../../content/applications/productivity/studio/pdf_reports.rstNone
 msgid "Configuration pop-up window for the default layout of PDF reports"
 msgstr ""
+"Ventana emergente de configuración para el diseño predeterminado de los "
+"reportes en PDF"
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:146
 msgid "Header and footer"
-msgstr ""
+msgstr "Encabezado y pie de página "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:148
 msgid ""
@@ -4873,6 +4912,13 @@ msgid ""
 "reports/header-footer/internal`, or :ref:`studio/pdf-reports/header-"
 "footer/blank`."
 msgstr ""
+"Al crear un reporte nuevo en Studio, primero debe elegir uno de entre tres "
+"estilos de reporte. Esto se usa para determinar qué encabezado y pie de "
+"página se mostrará. Para hcerlo, vaya a la aplicación en dónde quiere "
+"agregar un nuevo reporte, luego a el :menuselection:`Botón de Studio --> "
+"Reportes --> Crear` y seleccione :ref:`studio/pdf-reports/header-"
+"footer/external`, :ref:`studio/pdf-reports/header-footer/internal` o "
+":ref:`studio/pdf-reports/header-footer/blank`.    "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:157
 msgid "External"
@@ -4885,12 +4931,18 @@ msgid ""
 ":guilabel:`Company Name`, :guilabel:`Phone`, :guilabel:`Email`, and "
 ":guilabel:`Website`."
 msgstr ""
+"El encabezado muestra el :ref:`studio/pdf-reports/default-layout/logo` y "
+"varios valores establecidos en el modelo *Empresa*: el :guilabel:`Nombre de "
+"la empresa`, :guilabel:`Teléfono`, :guilabel:`Corre electrónico` y "
+":guilabel:`Sitio web`.     "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:164
 msgid ""
 "To change a company's information, go to :menuselection:`Settings --> "
 "Companies --> Update Info`."
 msgstr ""
+"Para cambiar la información de la empresa, vaya a :menuselection:`Ajustes "
+"--> Empresas --> Actualizar información`. "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rstNone
 msgid "Example of an External header"
@@ -5146,22 +5198,31 @@ msgid ""
 ":guilabel:`Name`: change the report name. The new name is applied everywhere"
 " (in Studio, under the :guilabel:`Print` button, and for the PDF file name)."
 msgstr ""
+":guilabel:`Nombre`: cambie el nombre del reporte. El nuevo nombre se cambia "
+"en todos lados (en Studio, en el botón :guilabel:`Imprimir` y para el nombre"
+" del archivo PDF). "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:296
 msgid ":guilabel:`Paper format`: change the paper size of the report."
 msgstr ""
+":guilabel:`Formato del papel`: cambie el tamaño del papel del reporte."
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:298
 msgid ""
 ":guilabel:`Add in print`: add the report under the :guilabel:`🖶 Print` "
 "button available on the record."
 msgstr ""
+":guilabel:`Agergar para imprimir`: agregue el reporte en el botón "
+":guilabel:`🖶 Imprimir` qie está disponible en el registro. "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:301
 msgid ""
 ":guilabel:`Limit visibility to groups`: limit the availability of the PDF "
 "report to specific :doc:`user groups <../../general/users/access_rights>`."
 msgstr ""
+":guilabel:`Visibilidad limitada a los grupos`: limíte la disponibilidad del "
+"reporte en PDF a :doc:`grupos de usuarios user groups "
+"<../../general/users/access_rights>` específicos. "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:305
 msgid "Options tab"
@@ -5187,34 +5248,42 @@ msgstr ""
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:317
 msgid "Below are presented some of the most common options:"
-msgstr ""
+msgstr "A continuación están algunas de las opciones más comunes: "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:319
 msgid ""
 ":guilabel:`Margins`: add spacing at the :guilabel:`top`, :guilabel:`right`, "
 ":guilabel:`bottom`, and :guilabel:`left` of the element."
 msgstr ""
+":guilabel:`Márgenes`: agaregue un espaciado en la parte "
+":guilabel:`superior`, :guilabel:`derecha`, :guilabel:`inferior`, e "
+":guilabel:`izquierda` del elemento. "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:322
 msgid ":guilabel:`Width`: set the element's maximum width."
-msgstr ""
+msgstr ":guilabel:`Ancho`: establezca el ancho máximo del elemento. "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:324
 msgid ""
 ":guilabel:`Visible if`: set under which condition(s) the element should be "
 "displayed."
 msgstr ""
+":guilabel:`Visible si`: establezca bajo que condición(es) se debe mostrar el"
+" elemento. "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:326
 msgid ""
 ":guilabel:`Visible for`: set for which :doc:`users groups "
 "<../../general/users/access_rights>` the element should be displayed."
 msgstr ""
+":guilabel:`Visible para`: establezca para qué :doc:`grupos de usuarios "
+"<../../general/users/access_rights>` se debe mostrar el elemento. "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:329
 msgid ""
 ":guilabel:`Remove from View`: remove the element from the report's view."
 msgstr ""
+":guilabel:`Quitar de la vista`: quitar el elemento de la vista del reporte."
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:331
 msgid ":guilabel:`Text decoration`: bold, italicize, and underline the font."
@@ -5227,14 +5296,19 @@ msgid ""
 ":guilabel:`Alignment`: align the element to the left, center, or right of "
 "the report."
 msgstr ""
+":guilabel:`Alineación`: alinee el elemento a la izquierda, al centro o a la "
+"derecha del reporte. "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:335
 msgid ":guilabel:`Font style`: use one of the default font styles."
 msgstr ""
+":guilabel:`Estilo de fuente`: use uno de los estilos de fuente predefinidos."
+" "
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:337
 msgid ":guilabel:`Colors`: change the font's color and the background color."
 msgstr ""
+":guilabel:`Colores`: cambie el color de la fuente y el color del fondo."
 
 #: ../../content/applications/productivity/studio/pdf_reports.rst:340
 msgid ""

locale/es/LC_MESSAGES/services.po

@@ -10,10 +10,11 @@
 # Jesse Garza <jga@odoo.com>, 2021
 # marcescu, 2022
 # Patricia Gutiérrez Capetillo <pagc@odoo.com>, 2022
-# Lucia Pacheco <lpo@odoo.com>, 2022
+# Lucia Pacheco, 2022
 # Pedro M. Baeza <pedro.baeza@tecnativa.com>, 2022
 # Martin Trigaux, 2023
 # Braulio D. López Vázquez <bdl@odoo.com>, 2023
+# Iran Villalobos López, 2023
 # 
 #, fuzzy
 msgid ""
@@ -22,7 +23,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-03-03 11:23+0000\n"
 "PO-Revision-Date: 2021-11-02 08:49+0000\n"
-"Last-Translator: Braulio D. López Vázquez <bdl@odoo.com>, 2023\n"
+"Last-Translator: Iran Villalobos López, 2023\n"
 "Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -1735,6 +1736,9 @@ msgid ""
 "assign activities to coworkers, and keep track of each project's "
 "profitability."
 msgstr ""
+"Proyecto de Odoo es una herramienta para gestionar sus proyectos activos. "
+"Planifique tareas, asigne actividades a sus compañeros de trabajo y "
+"mantengase al tanto del rendimiento de cada proyecto. "
 
 #: ../../content/applications/services/project.rst:14
 #: ../../content/applications/services/timesheets.rst:11

locale/nl/LC_MESSAGES/sphinx.po

@@ -10,6 +10,7 @@
 # Erwin van der Ploeg <erwin@odooexperts.nl>, 2022
 # Yenthe Van Ginneken <yenthespam@gmail.com>, 2023
 # Martin Trigaux, 2023
+# Jolien De Paepe, 2023
 # 
 #, fuzzy
 msgid ""
@@ -18,7 +19,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-01-02 09:09+0000\n"
 "PO-Revision-Date: 2022-03-18 15:03+0000\n"
-"Last-Translator: Martin Trigaux, 2023\n"
+"Last-Translator: Jolien De Paepe, 2023\n"
 "Language-Team: Dutch (https://app.transifex.com/odoo/teams/41243/nl/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -187,7 +188,7 @@ msgstr ""
 #: ../../extensions/odoo_theme/layout_templates/legal.html:78
 #: ../../extensions/odoo_theme/layout_templates/legal.html:80
 msgid "Read"
-msgstr ""
+msgstr "Lezen"
 
 #: ../../extensions/odoo_theme/layout_templates/legal.html:43
 #: ../../extensions/odoo_theme/layout_templates/legal.html:62