design update about the notice tag

Author: meganelepalud-akeneo

content/news/2022.md

@@ -11,7 +11,9 @@ In this section, you can filter tutorials per use case or feature.
 
 👉 Discover our [Guided tutorials](/tutorials/homepage.html) section
 
-### <span class="label label-news label-notice">NOTICE - UPDATED</span> Optional SKU
+### <span class="label label-news label-updated">UPDATED</span> <span class="label label-news label-notice">NOTICE</span> Optional SKU
+
+**⚠️ This update could have an impact on existing integrations.** 
 
 From November 2022, the product identifier value (pim_catalog_identifier attribute) has now become optional.
 
@@ -37,7 +39,9 @@ Additionally, **app users** are more autonomous by configuring their data select
 
 ## September 2022
 
-### <span class="label label-news label-notice">NOTICE - ADDED</span> Product UUID
+### <span class="label label-news label-added">ADDED</span> <span class="label label-news label-notice">NOTICE</span> Product UUID
+
+**⚠️ This update could have an impact on existing integrations.** 
 
 Akeneo PIM used to contain one and only identification: the 'identifier' field (the only `pim_catalog_identifier` attribute of the whole product). In Serenity, this field value is the SKU (Stock Keeping Unit) of the product, but what if you need to identify your product with several product identifiers (SKU, EAN, GTIN...)? Adding classic fields won't do the job you need a more flexible identifier field for each product. And you still need a way to identify your product if its SKU has changed.