[IMP] *: standardize spelling of “cancelled” across documentation

In https://github.com/odoo/odoo/pull/129722, we settled on using the spelling “cancelled”,
and removed all occurrences of “canceled” from the codebase.

This commit does the same for the documentation.

Task-3951276

closes odoo/documentation#9494

Signed-off-by: Vincent Larcin (vila) <vila@odoo.com>

content/developer/tutorials/server_framework_101/05_firstui.rst

@@ -277,7 +277,7 @@ Note that the default ``active=False`` value was assigned to all existing record
 .. exercise:: Add state field.
 
     Add a ``state`` field to the ``estate.property`` model. Five values are possible: New,
-    Offer Received, Offer Accepted, Sold and Canceled. It must be required, should not be copied
+    Offer Received, Offer Accepted, Sold and Cancelled. It must be required, should not be copied
     and should have its default value set to 'New'.
 
     Make sure to use the correct type!

content/developer/tutorials/server_framework_101/09_actions.rst

@@ -1,6 +1,6 @@
-==================================
+=================================
 Chapter 9: Ready For Some Action?
-==================================
+=================================
 
 So far we have mostly built our module by declaring fields and views. We just introduced business
 logic in the :doc:`previous chapter <08_compute_onchange>` thanks to
@@ -30,7 +30,7 @@ Object Type
         :align: center
         :alt: Cancel and set to sold
 
-    A canceled property cannot be sold and a sold property cannot be canceled. For the sake of
+    A cancelled property cannot be sold and a sold property cannot be cancelled. For the sake of
     clarity, the ``state`` field has been added on the view.
 
     - You should be able to accept or refuse an offer:
@@ -99,8 +99,8 @@ and its
 
 .. exercise:: Cancel and set a property as sold.
 
-    - Add the buttons 'Cancel' and 'Sold' to the ``estate.property`` model. A canceled property
-      cannot be set as sold, and a sold property cannot be canceled.
+    - Add the buttons 'Cancel' and 'Sold' to the ``estate.property`` model. A cancelled property
+      cannot be set as sold, and a sold property cannot be cancelled.
 
       Refer to the first image of the **Goal** for the expected result.
 

content/developer/tutorials/server_framework_101/11_sprinkles.rst

@@ -8,7 +8,7 @@ Our real estate module now makes sense from a business perspective. We created
 :doc:`constraints <10_constraints>`. However our user interface is still a bit
 rough. We would like to add some colors to the list views and make some fields and buttons conditionally
 disappear. For example, the 'Sold' and 'Cancel' buttons should disappear when the property
-is sold or canceled since it is no longer allowed to change the state at this point.
+is sold or cancelled since it is no longer allowed to change the state at this point.
 
 This chapter covers a very small subset of what can be done in the views. Do not hesitate to
 read the reference documentation for a more complete overview.
@@ -303,7 +303,7 @@ should not be displayed to the user, we can use the ``invisible`` attribute to h
       there is no garden.
     - Make the 'Accept' and 'Refuse' buttons invisible once the offer state is set.
     - Do not allow adding an offer when the property state is 'Offer Accepted', 'Sold' or
-      'Canceled'. To do this use the ``readonly`` attribute.
+      'Cancelled'. To do this use the ``readonly`` attribute.
 
 .. warning::
 

content/developer/tutorials/server_framework_101/12_inheritance.rst

@@ -17,7 +17,7 @@ Python Inheritance
 
     **Goal**: at the end of this section:
 
-    - It should not be possible to delete a property which is not new or canceled.
+    - It should not be possible to delete a property which is not new or cancelled.
 
     .. image:: 12_inheritance/unlink.gif
         :align: center
@@ -87,7 +87,7 @@ when you need to call the parent method with a modified recordset.
 
 .. exercise:: Add business logic to the CRUD methods.
 
-    - Prevent deletion of a property if its state is not 'New' or 'Canceled'
+    - Prevent deletion of a property if its state is not 'New' or 'Cancelled'
 
     Tip: create a new method with the :func:`~odoo.api.ondelete` decorator and remember that
     ``self`` can be a recordset with more than one record.