diff --git a/docs/commerce/cart/quick_order.md b/docs/commerce/cart/quick_order.md
index ec1b5ae68d..be5aa30eb3 100644
--- a/docs/commerce/cart/quick_order.md
+++ b/docs/commerce/cart/quick_order.md
@@ -6,7 +6,7 @@ edition: commerce
 # Quick order
 
 The quick order form allows users to efficiently process orders with multiple items in bulk through the storefront.
-Customers don't need to browse the countless store pages, they can fill in a provided form with products' SKU number and quantity, or upload their own list into the system directly.
+Customers don't need to browse the countless store pages, they can fill in a provided form with product code (SKU) and quantity, or upload their own list into the system directly.
 Quick order forms can be used by registered and guest users.
 
 ## Quick order flows
@@ -17,7 +17,7 @@ Customers can use one or both of the following methods to specify products and p
 
 1\. Customer clicks the **Quick order** link.
 
-2\. Provides products' SKU and quantity. At this point, no validation is provided.
+2\. Provides product code and quantity. At this point, no validation is provided.
 
 ![Customer enters individual products](img/quick_order_list.png)
 
@@ -31,11 +31,11 @@ Customers can use one or both of the following methods to specify products and p
 
 2\. Downloads a sample file from **Add your order** section.
 
-3\. Uses the template to fill in their order with products' SKU and quantity.
+3\. Uses the template to fill in their order with product code and quantity.
 
 4\. Uploads the filled in quick order file back to the system by drag and drop or file selection.
 
-5\. The file name appears in the **Add your order** section. At this point, only file validation is provided. The SKUs or product availability isn't validated.
+5\. The file name appears in the **Add your order** section. At this point, only file validation is provided. Product codes and availability aren't validated.
 
 ![Customer uploads list of products](img/quick_order_add_order.png)
 
@@ -48,7 +48,7 @@ Customers can use one or both of the following methods to specify products and p
 Orders from quick order are validated in the cart.
 There, the system checks if:
 
-- provided SKU is valid
+- provided product code is valid
 - provided products are available for purchase
 - requested quantities of products are available
 
@@ -85,4 +85,3 @@ ibexa:
                 batch_order:
                     processed_records_limit: 2000
 ```
-
diff --git a/docs/commerce/transactional_emails/transactional_emails_parameters.md b/docs/commerce/transactional_emails/transactional_emails_parameters.md
index 69d880baa4..a6a0efb842 100644
--- a/docs/commerce/transactional_emails/transactional_emails_parameters.md
+++ b/docs/commerce/transactional_emails/transactional_emails_parameters.md
@@ -48,7 +48,7 @@ If this extensive list of variables isn't sufficient, you can [extend it to incl
 | |shippingMethodTypeName|Technical name of shipping method type| | |
 | |shipmentStatus|Technical identifier of shipment status| |Only available in ShipmentStatusChange notification|
 |Product information|products.id|Product numerical ID|123|
-| |products.code|Product code, SKU|123456|
+| |products.code|Product code (SKU)|123456|
 | |products.name|Product name|iPhone 15 Pro 256GB Space Gray|
 | |products.url|Product view URL|https://example.com/product/iphone-15-pro-256gb-space-gray/|
 | |products.thumbnail|Product thumbnail URL|https://example.com/assets/images/iphone-15-pro-256gb-space-gray.jpg|
@@ -62,4 +62,4 @@ If this extensive list of variables isn't sufficient, you can [extend it to incl
 | |userEmail|User e-mail address|john.doe@example.com|
 | |userName|User name|John Doe|
 |Password reset|token|Token used to reset password|5bcc871f1a966db58c06187369813447|
-| |passwordResetUrl|Absolute URL to reset password|http://example.com/user/reset-password/5bcc871f1a966db58c06187369813447|
\ No newline at end of file
+| |passwordResetUrl|Absolute URL to reset password|http://example.com/user/reset-password/5bcc871f1a966db58c06187369813447|
diff --git a/docs/content_management/content_management_guide.md b/docs/content_management/content_management_guide.md
index a938d6d48f..8d6422a3c2 100644
--- a/docs/content_management/content_management_guide.md
+++ b/docs/content_management/content_management_guide.md
@@ -268,6 +268,6 @@ individual products can have multiple variants with differing related assets, pr
 
 ### B2B store
 
-Extensive content management capabilities would prove themselves in a setting, where multiple buyers from different partner companies connect to an industry leader’s trading website, and they expect to find well organized SKU catalogs that contain basic product information.
+Extensive content management capabilities would prove themselves in a setting, where multiple buyers from different partner companies connect to an industry leader’s trading website, and they expect to find well organized product code (SKU) catalogs that contain basic product information.
 From there they would like to access detailed specifications, white papers and application notes.
 The same products could come with different brands and at different price points, depending on the customer segment or origin.
diff --git a/docs/content_management/field_types/field_type_storage.md b/docs/content_management/field_types/field_type_storage.md
index 2e2aa0f5a8..82fcd244d0 100644
--- a/docs/content_management/field_types/field_type_storage.md
+++ b/docs/content_management/field_types/field_type_storage.md
@@ -182,7 +182,7 @@ In this case it's recommended to either create base implementation which each ga
 
 Just like in the case of data, storing [field type settings](type_and_value.md#field-type-settings) in content item tables may prove insufficient.
 It's not a problem if your setting specifies, for example, the allowed number of characters in a text field.
-However, the field type may represent a more complex object, for example, it may consist of two or more other fields, such as the name, SKU, and price, and there can be a set of default values instead of just one.
+However, the field type may represent a more complex object, for example, it may consist of two or more other fields, such as the name, product code (SKU), and price, and there can be a set of default values instead of just one.
 Once you add validation rules for these field values, then it becomes an issue.
 
 You can overcome this obstacle:
diff --git a/docs/update_and_migration/from_4.5/update_from_4.5.md b/docs/update_and_migration/from_4.5/update_from_4.5.md
index b4b096f723..aed5c45213 100644
--- a/docs/update_and_migration/from_4.5/update_from_4.5.md
+++ b/docs/update_and_migration/from_4.5/update_from_4.5.md
@@ -356,7 +356,7 @@ php bin/console ibexa:migrations:migrate --file=2023_12_07_20_23_editor_content_
 
 Site context is used in content tree to display only those content items that belong to the selected website.
 
-You can add locations that shoudn't be publicly accessible to the list of excluded paths:
+You can add locations that shouldn't be publicly accessible to the list of excluded paths:
 
 ```yaml
 # /config/packages/ibexa_site_context.yaml