[MERGE] Forward-port of branch 13.0 to 14.0

content/applications/productivity/studio/concepts/understanding_automated_actions.rst

@@ -50,7 +50,7 @@ For every Trigger option, **conditions** can be applied, such as:
 - *Send Email*: an automatic :doc:`email <../../discuss/advanced/email_template>` is sent.
 - *Add Followers*: followers are notified of changes in the task.
 - *Create Next Activity*: creates an activity such as: *Call*, *Email*, *Reminder*.
-- *Send SMS Text Message*: sends an :doc:`SMS <../../../marketing/sms_marketing/pricing/pricing_and_faq>`.
+- *Send SMS Text Message*: sends an :doc:`SMS </applications/marketing/sms_marketing/pricing/pricing_and_faq>`.
 
 Example
 ~~~~~~~

content/applications/productivity/studio/how_to/reports.rst

@@ -34,7 +34,7 @@ them. Fields with related objects have their directives shown on *Field Expressi
 | Under **Visible if**, define the rule(s) to set visibility conditions to fields.
 | Example: if choosing to display a product image, you could set a visibility rule to only display
   the ones that are *set* in the product form, avoiding having a plain icon when they are not set.
-| **Visible for** is used to set which :doc:`groups <../../../general/odoo_basics/users>`
+| **Visible for** is used to set which :doc:`groups </applications/general/odoo_basics/users>`
   can have access to specific elements in the report. **Limit visibility to groups**, under
   *Report*, sets the visibility of the report to specifics groups, meaning that users belonging to
   other groups do not see the same final document.
@@ -50,7 +50,7 @@ added to the *Print* menu list on its respective document form.
    :align: center
    :alt: View of an invoice form emphasizing the menu print for Odoo Studio
 
-If activating the :doc:`Developer mode <../../../general/developer_mode/activate>`, additional fields
+If activating the :doc:`Developer mode </applications/general/developer_mode/activate>`, additional fields
 such as *Class* under *Options*, and *Reload from attachment* under *Report*, become visible.
 
 - *Class*: add custom CSS classes to the selected element (e.g. Bootstrap classes such as

content/applications/productivity/studio/use_cases/models_fields.rst

@@ -116,7 +116,7 @@ Administrator* or managers.
 
 - **Case scenario 5: change the tooltip of a field for all views.**
 
-| Activate the :doc:`Developer mode <../../../general/developer_mode/activate>` and open Studio.
+| Activate the :doc:`Developer mode </applications/general/developer_mode/activate>` and open Studio.
 | Select the necessary field and, under *Properties*, click on *More* to write your tooltip message
   on *Field Help*. The tooltip message is the explanatory message shown when the user hovers the
   field. The message here written is displayed on all views forms where the field is added.