Update from SAP DITA CMS (squashed):

commit 296c5b6f2b00eb705c82f987cdb02086452ce64f
Author: REDACTED
Date:   Mon May 12 06:31:33 2025 +0000

    Update from SAP DITA CMS 2025-05-12 06:31:33

    Project: dita-all/krj1744379789461
    Project map: 2b9bcd51c53b4d89b885a3e850c7601e.ditamap
    Output: loioa82e269bbb584cfcbdbd3ae8765d8e7f
    Language: en-US
    Builddable map: 5cbe4e5b4a19479a92b1d32ff23b7b63.ditamap

commit 4e14eaa4431bc940e0bfdb1f04fe9691c35b0c97
Author: REDACTED
Date:   Fri Mar 14 14:22:33 2025 +0100

    Create REUSE.toml

commit 5cf6b7cf70b9aa8f34f74b62450d296d403841b0
Author: REDACTED
Date:   Fri Mar 14 13:21:46 2025 +0000

    Update from SAP DITA CMS 2025-03-14 13:21:46

    Project: dita-all/ely1739543650700
    Project map: 2b9bcd51c53b4d89b885a3e850c7601e.ditamap
    Output: loioa82e269bbb584cfcbdbd3ae8765d8e7f
    Language: en-US
    Builddable map: 5cbe4e5b4a19479a92b1d32ff23b7b63.ditamap

commit ba3e6e792681af52fb45841698b7168e69648ee5
Author: REDACTED

##################################################
[Remaining squash message was removed before commit...]

Author: ditaccms-bot

docs/03_Get-Started/step-8-translatable-texts-typescript-4dcf52e.md

@@ -31,7 +31,7 @@ You can view all files at [OpenUI5 TypeScript Walkthrough - Step 8: Translatable
 
 ## webapp/i18n/i18n.properties \(New\)
 
-The `i18n` file allows you to store translated texts for multiple languages, making your application accessible to a wider audience. In order to achive this, the `properties` file for texts contains name-value pairs for each element. You can add any number of parameters to the texts by enclosing them in curly brackets with corresponding numbers. These numbers correspond to the sequence in which the parameters are accessed \(starting with 0\).
+The `i18n` file allows you to store translated texts for multiple languages, making your application accessible to a wider audience. In oder to achive this, the `properties` file for texts contains name-value pairs for each element. You can add any number of parameters to the texts by enclosing them in curly brackets with corresponding numbers. These numbers correspond to the sequence in which the parameters are accessed \(starting with 0\).
 
 To set up the `i18n` file, we navigate to the `webapp` folder and create a new folder named `i18n`. Inside this folder, we place an `i18n.properties` file, which serves as a storage for our translated texts. We add two name-value pairs to our properties file: The `showHelloButtonText` name represents the text for the button on our app view. The `helloMsg` name represents the greeting message we'll display in the message toast. To include the appropriate recipient's name in the message, we use a placeholder with the greeting message text.
 

docs/05_Developing_Apps/content-security-policy-fe1a6db.md

@@ -603,23 +603,6 @@ Hyphenation
 
 When native hyphenation is not available, a third-party library \(Hyphenopoly\) is used. This library uses WASM, which leads to CSP issues due to browser limitations. There is a fallback to `asm.js`, if WASM can't be used.
 
-</td>
-</tr>
-<tr>
-<td valign="top">
-
-`sap.ndc.BarcodeScanner`
-
-</td>
-<td valign="top">
-
-BarcodeScanner
-
-</td>
-<td valign="top">
-
-`script-src` requires `wasm-unsafe-eval`
-
 </td>
 </tr>
 <tr>

docs/06_SAP_Fiori_Elements/adding-confirmation-popovers-for-actions-87130de.md

@@ -40,5 +40,7 @@ To display a confirmation popover, add the `IsActionCritical` annotation to your
 
 <a name="loio87130de10c8a44269c605b0322df6b1a__section_acx_1nn_dzb"/>
 
+## Additional Features in SAP Fiori Elements for OData V2
+
 Apps can add action-specific messages to confirmation dialog boxes. For more information, see [Localization of UI Texts](localization-of-ui-texts-b8cb649.md).