OpenUI5 Documentation Update 09.02.2024

Author: openui5bot

docs/Step_26_Mock_Server_Configuration_TypeScript_3e1c64f.md

@@ -34,9 +34,9 @@ You can view all files at [OpenUI5 TypeScript Walkthrough - Step 26: Mock Server
 
 **Folder Structure for this Step**
 
+![The graphic has an explanatory text](images/loio0ed199908e9a4dbda15412b9205f622c_LowRes.png "Folder Structure for this Step")
 
-
-![The graphic has an explanatory text](images/loio0ed199908e9a4dbda15412b9205f622c_LowRes.png)The folder structure of our app project is clearly separating test and productive files after this step. The new `test` folder now contains a new HTML page `mockServer.html` which will launch our application in test mode without calling the real service.
+The folder structure of our app project is clearly separating test and productive files after this step. The new `test` folder now contains a new HTML page `mockServer.html` which will launch our application in test mode without calling the real service.
 
 The new `localService` folder contains a `metadata.xml` service description file for OData, the `mockserver.js` file that simulates a real service with local data, and the `mockdata` subfolder that contains the local test data \(`Invoices.json`\).
 

docs/Step_27_Unit_Test_with_QUnit_TypeScript_750c8c1.md

@@ -37,9 +37,9 @@ You can view all files at [OpenUI5 TypeScript Walkthrough - Step 27: Unit Tests
 
 **Folder Structure for this Step**
 
+![The graphic has an explanatory text](images/loioeae0f42249494ae7aeda044e83f15097_LowRes.png "Folder Structure for this Step")
 
-
-![The graphic has an explanatory text](images/loioeae0f42249494ae7aeda044e83f15097_LowRes.png)We add a new folder `unit` under the `test` folder and a `model` subfolder where we will place our formatter unit test. The folder structure matches the app structure to easily find the corresponding unit tests.
+We add a new folder `unit` under the `test` folder and a `model` subfolder where we will place our formatter unit test. The folder structure matches the app structure to easily find the corresponding unit tests.
 
 ***
 

docs/Step_28_Integration_Test_with_OPA_TypeScript_412f0b6.md

@@ -37,9 +37,9 @@ You can view all files at [OpenUI5 TypeScript Walkthrough - Step 28: Integration
 
 **Folder Structure for this Step**
 
+![The graphic has an explanatory text](images/loio27e84d5bd72a485498564b92894869b5_LowRes.png "Folder Structure for this Step")
 
-
-![The graphic has an explanatory text](images/loio27e84d5bd72a485498564b92894869b5_LowRes.png)We add a new folder `integration` below the `test` folder, where we put our new test cases. Page objects that help structuring such integration tests are put in the `pages` subfolder that we also create now.
+We add a new folder `integration` below the `test` folder, where we put our new test cases. Page objects that help structuring such integration tests are put in the `pages` subfolder that we also create now.
 
 ***
 

docs/Step_9_Component_Configuration_TypeScript_f9d0e2f.md

@@ -33,9 +33,9 @@ You can view all files at [OpenUI5 TypeScript Walkthrough - Step 9: Component Co
 
 
 
-**Figure: Folder Structure for this Step**
+**Folder Structure for this Step**
 
-![The graphic has an explanatory text](images/loioaa6ba83cdebc4a75be6a6b2ff6efffcb_LowRes.png "Figure: Folder Structure for this Step")
+![The graphic has an explanatory text](images/loioaa6ba83cdebc4a75be6a6b2ff6efffcb_LowRes.png "Folder Structure for this Step")
 
 After this step your project structure will look like the figure above. We'll create the `Component.ts` file now and modify the related files in the app.
 

docs/sap_ui_mdc_experimental_1dd2aa9.md

@@ -106,5 +106,5 @@ The following graphic illustrates this behavior:
 
 [Samples](https://sdk.openui5.org/entity/sap.ui.mdc)
 
-[OpenUI5 MDC Tutorial](https://github.com/SAP-samples/ui5-mdc-json-tutorial)
+[UI5 MDC Tutorial](https://github.com/SAP-samples/ui5-mdc-json-tutorial)