UI5 · petermuessig · Aug 6, 2026 · Aug 4, 2026
diff --git a/packages/databinding/steps/01/README.md b/packages/databinding/steps/01/README.md
@@ -215,7 +215,7 @@ server:
 
 ***
 
-**Next:** [Step 2: Creating a Model](../02/README.md "In this step, we create a model. It serves as a container for the data your application operates on.")
+**Next:** [Step 2: Creating a Model](../02/README.md)
 
 ***
 

diff --git a/packages/databinding/steps/02/README.md b/packages/databinding/steps/02/README.md
@@ -86,9 +86,9 @@ The text that is displayed on the UI is still hard-coded and not taken from the
 
 ***
 
-**Next:** [Step 3: Create Property Binding](../03/README.md "Although there is no visible difference, the text on the screen is now derived from model data.")
+**Next:** [Step 3: Create Property Binding](../03/README.md)
 
-**Previous:** [Step 1: No Data Binding](../01/README.md "In this step, we create a basic application and simply place some text on the screen using a standard sap.m.Text control.")
+**Previous:** [Step 1: No Data Binding](../01/README.md)
 
 ***
 

diff --git a/packages/databinding/steps/03/README.md b/packages/databinding/steps/03/README.md
@@ -40,9 +40,9 @@ Assign the `text` property of the `sap.m.Text` control to the value `{/greetingT
 
 ***
 
-**Next:** [Step 4: Two-Way Data Binding](../04/README.md "In the examples we've looked at so far, we've displayed the value of a model property using a read-only field.")
+**Next:** [Step 4: Two-Way Data Binding](../04/README.md)
 
-**Previous:** [Step 2: Creating a Model](../02/README.md "In this step, we create a model.")
+**Previous:** [Step 2: Creating a Model](../02/README.md)
 
 ***
 

diff --git a/packages/databinding/steps/04/README.md b/packages/databinding/steps/04/README.md
@@ -100,9 +100,9 @@ Two things are happening here:
 
 ***
 
-**Next:** [Step 5: One-Way Data Binding](../05/README.md "Unlike the two-way binding behavior we've seen, one-way data binding is also possible.")
+**Next:** [Step 5: One-Way Data Binding](../05/README.md)
 
-**Previous:** [Step 3: Create Property Binding](../03/README.md "Although there is no visible difference, the text on the screen is now derived from model data.")
+**Previous:** [Step 3: Create Property Binding](../03/README.md)
 
 ***
 

diff --git a/packages/databinding/steps/05/README.md b/packages/databinding/steps/05/README.md
@@ -90,6 +90,6 @@ If you wish to alter the binding mode, you've got two options:
 
 ***
 
-**Next:** [Step 6: Resource Models](../06/README.md "Business applications often require language-specific \(translatable\) text used as labels and descriptions on the user interface.")
+**Next:** [Step 6: Resource Models](../06/README.md)
 
-**Previous:** [Step 4: Two-Way Data Binding](../04/README.md "In the examples we've looked at so far, we've displayed the value of a model property using a read-only field.")
+**Previous:** [Step 4: Two-Way Data Binding](../04/README.md)
diff --git a/packages/databinding/steps/06/README.md b/packages/databinding/steps/06/README.md
@@ -199,9 +199,9 @@ You can use multiple model instances by using different model names. The model n
 
 ***
 
-**Next:** [Step 7: \(Optional\) Resource Bundles and Multiple Languages](../07/README.md "Resource bundles exist to enable an app to run in multiple languages without the need to change any code.")
+**Next:** [Step 7: \(Optional\) Resource Bundles and Multiple Languages](../07/README.md)
 
-**Previous:** [Step 5: One-Way Data Binding](../05/README.md "Unlike the two-way binding behavior we've seen, one-way data binding is also possible.")
+**Previous:** [Step 5: One-Way Data Binding](../05/README.md)
 
 ***
 

diff --git a/packages/databinding/steps/07/README.md b/packages/databinding/steps/07/README.md
@@ -53,9 +53,9 @@ To check the result, append the `sap-language=DE` URL parameter to the URL in yo
 
 ***
 
-**Next:** [Step 8: Binding Paths: Accessing Properties in Hierarchically Structured Models](../08/README.md "Let's explore how to reference fields in a hierarchically structured model object.")
+**Next:** [Step 8: Binding Paths: Accessing Properties in Hierarchically Structured Models](../08/README.md)
 
-**Previous:** [Step 6: Resource Models](../06/README.md "Business applications often require language-specific (translatable) text used as labels and descriptions on the user interface.")
+**Previous:** [Step 6: Resource Models](../06/README.md)
 
 ***
 

diff --git a/packages/databinding/steps/08/README.md b/packages/databinding/steps/08/README.md
@@ -123,9 +123,9 @@ panel2HeaderText=Adressdetails
 
 ***
 
-**Next:** [Step 9: Formatting Values](../09/README.md "We'd also like to provide our users with a way of contacting Harry Hawk, so we're adding a link that sends an e-mail to Harry.")
+**Next:** [Step 9: Formatting Values](../09/README.md)
 
-**Previous:** [Step 7: \(Optional\) Resource Bundles and Multiple Languages](../07/README.md "Resource bundles exist to enable an app to run in multiple languages without the need to change any code.")
+**Previous:** [Step 7: \(Optional\) Resource Bundles and Multiple Languages](../07/README.md)
 
 ***
 

diff --git a/packages/databinding/steps/09/README.md b/packages/databinding/steps/09/README.md
@@ -161,9 +161,9 @@ mailBody=Wie geht es dir?
 
 ***
 
-**Next:** [Step 10: Property Formatting Using Data Types](../10/README.md "OpenUI5 offers a set of simple data types, including Boolean, Currency, Date and Float.")
+**Next:** [Step 10: Property Formatting Using Data Types](../10/README.md)
 
-**Previous:** [Step 8: Binding Paths: Accessing Properties in Hierarchically Structured Models](../08/README.md "In Step 6, we stated that the fields in a resource model are arranged in a flat structure; in other words, there is no hierarchy of properties.")
+**Previous:** [Step 8: Binding Paths: Accessing Properties in Hierarchically Structured Models](../08/README.md)
 
 ***
 

diff --git a/packages/databinding/steps/10/README.md b/packages/databinding/steps/10/README.md
@@ -133,9 +133,9 @@ salesAmount=Verk\u00e4ufe bis zum heutigen Datum
 
 ***
 
-**Next:** [Step 11: Validation Using `sap/ui/core/Messaging`](../11/README.md "Up to this point, we've created a currency field that formats itself correctly. The currency data type can also validate user input to ensure it meets currency requirements.")
+**Next:** [Step 11: Validation Using `sap/ui/core/Messaging`](../11/README.md)
 
-**Previous:** [Step 9: Formatting Values](../09/README.md "We'd also like to provide our users with a way of contacting Harry Hawk, so we're adding a link that sends an e-mail to Harry.")
+**Previous:** [Step 9: Formatting Values](../09/README.md)
 
 ***
 

diff --git a/packages/databinding/steps/11/README.md b/packages/databinding/steps/11/README.md
@@ -60,9 +60,9 @@ However, the error message only displays when that particular field is in focus:
 
 ***
 
-**Next:** [Step 12: Aggregation Binding Using Templates](../12/README.md "Aggregation binding, also known as list binding, lets a control bind to a list within the model data.")
+**Next:** [Step 12: Aggregation Binding Using Templates](../12/README.md)
 
-**Previous:** [Step 10: Property Formatting Using Data Types](../10/README.md "OpenUI5 offers a set of simple data types, including Boolean, Currency, Date and Float.")
+**Previous:** [Step 10: Property Formatting Using Data Types](../10/README.md)
 
 ***
 

diff --git a/packages/databinding/steps/12/README.md b/packages/databinding/steps/12/README.md
@@ -294,9 +294,9 @@ stockValue=Lagerbestand Wert
 
 ***
 
-**Next:** [Step 13: Element Binding](../13/README.md "Now, let's do something with that newly generated list.")
+**Next:** [Step 13: Element Binding](../13/README.md)
 
-**Previous:** [Step 11: Validation Using `sap/ui/core/Messaging`](../11/README.md "Up to this point, we've created a currency field that formats itself correctly.")
+**Previous:** [Step 11: Validation Using `sap/ui/core/Messaging`](../11/README.md)
 
 ***
 

diff --git a/packages/databinding/steps/13/README.md b/packages/databinding/steps/13/README.md
@@ -201,9 +201,9 @@ Now, you can click on an element in the list and view its details in the panel b
 
 ***
 
-**Next:** [Step 14: Expression Binding](../14/README.md "An expression binding lets you display a calculated value on the screen, which is derived from values found in a model object.")
+**Next:** [Step 14: Expression Binding](../14/README.md)
 
-**Previous:** [Step 12: Aggregation Binding Using Templates](../12/README.md "Aggregation binding, also known as list binding, lets a control bind to a list within the model data.")
+**Previous:** [Step 12: Aggregation Binding Using Templates](../12/README.md)
 
 ***
 

diff --git a/packages/databinding/steps/14/README.md b/packages/databinding/steps/14/README.md
@@ -138,9 +138,9 @@ The ampersand \(`&`\) character also has a high-priority meaning to the XML pars
 
 ***
 
-**Next:** [Step 15: Aggregation Binding Using a Factory Function](../15/README.md "Instead of using a single hard-coded template control, we now opt for a factory function to generate different controls based on the data received at runtime.")
+**Next:** [Step 15: Aggregation Binding Using a Factory Function](../15/README.md)
 
-**Previous:** [Step 13: Element Binding](../13/README.md "Now, let's do something with that newly generated list.")
+**Previous:** [Step 13: Element Binding](../13/README.md)
 
 ***
 

diff --git a/packages/databinding/steps/15/README.md b/packages/databinding/steps/15/README.md
@@ -236,7 +236,7 @@ Congratulations! You've completed the Data Binding tutorial.
 
 ***
 
-**Previous:** [Step 14: Expression Binding](../14/README.md "An expression binding lets you display a calculated value on the screen, which is derived from values found in a model object.")
+**Previous:** [Step 14: Expression Binding](../14/README.md)
 
 ***
 

diff --git a/packages/quickstart/steps/01/README.md b/packages/quickstart/steps/01/README.md
@@ -342,7 +342,7 @@ npm start
 
 ***
 
-**Next:** [Step 2: Steady...](../02/README.md "Before we can do something with UI5, we need to laod and initialize it. This process of loading and initializing UI5 is called bootstrapping. Once this bootstrapping is finished, we simply display an alert.")
+**Next:** [Step 2: Steady...](../02/README.md)
 
 ***
 

diff --git a/packages/quickstart/steps/02/README.md b/packages/quickstart/steps/02/README.md
@@ -111,7 +111,7 @@ sap.ui.define([
 You can see a title bar and a blue button that reacts to your input. Congratulations, you have created our very first app.
 
 
-**Next:** [Step 3: Go!](../03/README.md "Before we can do something with UI5, we need to laod and initialize it. This process of loading and initializing UI5 is called bootstrapping. Once this bootstrapping is finished, we simply display an alert.")
+**Next:** [Step 3: Go!](../03/README.md)
 
 ***
 

diff --git a/packages/walkthrough/steps/01/README.md b/packages/walkthrough/steps/01/README.md
@@ -161,7 +161,7 @@ This will open a new browser window hosting your newly created `index.html`.
 
 ***
 
-**Next:** [Step 2: Bootstrap](../02/README.md "Before we can do something with UI5, we need to laod and initialize it. This process of loading and initializing UI5 is called bootstrapping. Once this bootstrapping is finished, we simply display an alert.")
+**Next:** [Step 2: Bootstrap](../02/README.md)
 
 ***
 

diff --git a/packages/walkthrough/steps/02/README.md b/packages/walkthrough/steps/02/README.md
@@ -248,9 +248,9 @@ Now you can benefit from live reload on changes and built framework resources at
 
 ***
 
-**Next:** [Step 3: Controls](../03/README.md "Now it's time to build our first little UI by replacing the Hello World text in the HTML body by the OpenUI5 control sap.m.Text. In the beginning, we will use the TypeScript control API to set up the UI, the control instance is then placed into the HTML body‚")
+**Next:** [Step 3: Controls](../03/README.md)
 
-**Previous:** [Step 1: Hello World!](../01/README.md "As you know OpenUI5 is all about HTML5. Let's get started with building a first Hello World with only HTML. In addition we will initialize the UI5 CLI, so we can benefit from it from the beginning.")
+**Previous:** [Step 1: Hello World!](../01/README.md)
 
 ***
 

diff --git a/packages/walkthrough/steps/03/README.md b/packages/walkthrough/steps/03/README.md
@@ -134,9 +134,9 @@ ui5 add sap.m
 
 ***
 
-**Next:** [Step 4: XML Views](../04/README.md "Putting all our UI into the index.html file will very soon result in a messy setup and there is quite a bit of work ahead of us. So let’s do a first modularization by putting the sap/m/Text control into a dedicated view.")
+**Next:** [Step 4: XML Views](../04/README.md)
 
-**Previous:** [Step 2: Bootstrap](../02/README.md "Before we can do something with OpenUI5, we need to load and initialize it. This process of loading and initializing OpenUI5 is called bootstrapping. Once this bootstrapping is finished, we simply display an alert.")
+**Previous:** [Step 2: Bootstrap](../02/README.md)
 
 ***
 

diff --git a/packages/walkthrough/steps/04/README.md b/packages/walkthrough/steps/04/README.md
@@ -104,9 +104,9 @@ We have now embed our app view to the body of the HTML document.
 
 ***
 
-**Next:** [Step 5: Controllers](../05/README.md "In this step, we replace the text with a button and show the Hello World message when the button is pressed. The handling of the button's press event is implemented in the controller of the view.")
+**Next:** [Step 5: Controllers](../05/README.md)
 
-**Previous:** [Step 3: Controls](../03/README.md "Now it's time to build our first little UI by replacing the Hello World text in the HTML body by the OpenUI5 control sap.m.Text. In the beginning, we will use the TypeScript control AOI to set up the UI, the control instance is then placed into the HTML body.")
+**Previous:** [Step 3: Controls](../03/README.md)
 
 ***
 

diff --git a/packages/walkthrough/steps/05/README.md b/packages/walkthrough/steps/05/README.md
@@ -106,9 +106,9 @@ A view does not necessarily need an explicitly assigned controller. You do not h
 
 ***
 
-**Next:** [Step 6: Modules](../06/README.md "In OpenUI5, resources are often referred to as modules. In this step, we replace the alert from the last exercise with a proper Message Toast from the `sap.m` library.")
+**Next:** [Step 6: Modules](../06/README.md)
 
-**Previous:** [Step 4: XML Views](../04/README.md "Putting all our UI into the index.html file will very soon result in a messy setup and there is quite a bit of work ahead of us. So let’s do a first modularization by putting the sap/m/Text control into a dedicated view.")
+**Previous:** [Step 4: XML Views](../04/README.md)
 
 ***
 

diff --git a/packages/walkthrough/steps/06/README.md b/packages/walkthrough/steps/06/README.md
@@ -67,9 +67,9 @@ For now, the message toast just displays a static "Hello World" message. We will
 
 ***
 
-**Next:** [Step 7: JSON Model](../07/README.md "Now that we have set up the view and controller, it’s about time to think about the M in MVC.")
+**Next:** [Step 7: JSON Model](../07/README.md)
 
-**Previous:** [Step 5: Controllers](../05/README.md "In this step, we replace the text with a button and show the Hello World message when the button is pressed. The handling of the button's press event is implemented in the controller of the view.")
+**Previous:** [Step 5: Controllers](../05/README.md)
 
 ***
 

diff --git a/packages/walkthrough/steps/07/README.md b/packages/walkthrough/steps/07/README.md
@@ -126,9 +126,9 @@ In addition to this, we create a greeting message. We combine the static text "H
 
 ***
 
-**Next:** [Step 8: Translatable Texts](../08/README.md "In this step we move the texts of our UI to a separate resource file.")
+**Next:** [Step 8: Translatable Texts](../08/README.md)
 
-**Previous:** [Step 6: Modules](../06/README.md "In OpenUI5, resources are often referred to as modules. In this step, we replace the alert from the last exercise with a proper Message Toast from the `sap.m` library.")
+**Previous:** [Step 6: Modules](../06/README.md)
 
 ***
 

diff --git a/packages/walkthrough/steps/08/README.md b/packages/walkthrough/steps/08/README.md
@@ -178,9 +178,9 @@ A resource bundle is a flat structure, therefore the preceding slash \(/\) can b
 
 ***
 
-**Next:** [Step 9: Component Configuration](../09/README.md "After we have introduced all three parts of the Model-View-Controller \(MVC\) concept, we now come to another important structural aspect of OpenUI5.")
+**Next:** [Step 9: Component Configuration](../09/README.md)
 
-**Previous:** [Step 7: JSON Model](../07/README.md "Now that we have set up the view and controller, it’s about time to think about the M in MVC.")
+**Previous:** [Step 7: JSON Model](../07/README.md)
 
 ***
 

diff --git a/packages/walkthrough/steps/09/README.md b/packages/walkthrough/steps/09/README.md
@@ -246,9 +246,9 @@ sap.ui.define(["sap/ui/core/ComponentContainer"], function (ComponentContainer)
 
 ***
 
-**Next:** [Step 10: Manifest (Descriptor for Applications)](../10/README.md "All application-specific configuration settings will now further be put into the manifest. This clearly separates the application coding from the configuration settings and makes our app even more flexible.")
+**Next:** [Step 10: Manifest (Descriptor for Applications)](../10/README.md)
 
-**Previous:** [Step 8: Translatable Texts](../08/README.md "In this step we move the texts of our UI to a separate resource file.")
+**Previous:** [Step 8: Translatable Texts](../08/README.md)
 
 &nbsp;
 ***

diff --git a/packages/walkthrough/steps/10/README.md b/packages/walkthrough/steps/10/README.md
@@ -267,9 +267,9 @@ We can now delete our `index.ts/.js` file, because our component is now initiate
 
 ***
 
-**Next:** [Step 11: Pages and Panels](../11/README.md "After all the work on the app structure it’s time to improve the look of our app. We will use two controls from the sap.m library to add a bit more bling to our UI. You will also learn about control aggregations in this step.")
+**Next:** [Step 11: Pages and Panels](../11/README.md)
 
-**Previous:** [Step 9: Component Configuration](../09/README.md "After we have introduced all three parts of the Model-View-Controller \(MVC\) concept, we now come to another important structural aspect of OpenUI5.")
+**Previous:** [Step 9: Component Configuration](../09/README.md)
 
 ***
 

diff --git a/packages/walkthrough/steps/11/README.md b/packages/walkthrough/steps/11/README.md
@@ -92,9 +92,9 @@ The `App` control does the following important things for us:
 
 ***
 
-**Next:** [Step 12: Shell Control as Container](../12/README.md "Now we use a shell control as container for our app and use it as our new root element. The shell takes care of visual adaptation of the application to the device’s screen size by introducing a so-called letterbox on desktop screens.")
+**Next:** [Step 12: Shell Control as Container](../12/README.md)
 
-**Previous:** [Step 10: Manifest (Descriptor for Applications)](../10/README.md "All application-specific configuration settings will now further be put into the manifest. This clearly separates the application coding from the configuration settings and makes our app even more flexible.")
+**Previous:** [Step 10: Manifest (Descriptor for Applications)](../10/README.md)
 
 ***
 

diff --git a/packages/walkthrough/steps/12/README.md b/packages/walkthrough/steps/12/README.md
@@ -67,9 +67,9 @@ There are further options to customize the shell, like setting a custom backgrou
 
 ***
 
-**Next:** [Step 13: Margins and Paddings](../13/README.md "Our app content is still glued to the corners of the letterbox. To fine-tune our layout, we can add margins and paddings to the controls that we added in the previous step.")
+**Next:** [Step 13: Margins and Paddings](../13/README.md)
 
-**Previous:** [Step 11: Pages and Panels](../11/README.md "After all the work on the app structure it’s time to improve the look of our app. We will use two controls from the sap.m library to add a bit more &quot;bling&quot; to our UI. You will also learn about control aggregations in this step.")
+**Previous:** [Step 11: Pages and Panels](../11/README.md)
 
 ***
 

diff --git a/packages/walkthrough/steps/13/README.md b/packages/walkthrough/steps/13/README.md
@@ -80,9 +80,9 @@ To format the output text individually, we remove the description from the input
 
 ***
 
-**Next:** [Step 14: Custom CSS and Theme Colors](../14/README.md "Sometimes we need to define some more fine-granular layouts and this is when we can use the flexibility of CSS by adding custom style classes to controls and style them as we like.")
+**Next:** [Step 14: Custom CSS and Theme Colors](../14/README.md)
 
-**Previous:** [Step 12: Shell Control as Container](../12/README.md "Now we use a shell control as container for our app and use it as our new root element. The shell takes care of visual adaptation of the application to the device’s screen size by introducing a so-called letterbox on desktop screens.")
+**Previous:** [Step 12: Shell Control as Container](../12/README.md)
 
 ***
 

diff --git a/packages/walkthrough/steps/14/README.md b/packages/walkthrough/steps/14/README.md
@@ -133,9 +133,9 @@ The actual color now depends on the selected theme which ensures that the color
 **Related Information**  
 
 
-**Next:** [Step 15: Nested Views](../15/README.md "Our panel content is getting more and more complex and now it is time to move the panel content to a separate view. With that approach, the application structure is much easier to understand, and the individual parts of the app can be reused.")
+**Next:** [Step 15: Nested Views](../15/README.md)
 
-**Previous:** [Step 13: Margins and Paddings](../13/README.md "Our app content is still glued to the corners of the letterbox. To fine-tune our layout, we can add margins and paddings to the controls that we added in the previous step.")
+**Previous:** [Step 13: Margins and Paddings](../13/README.md)
 
 ***
 

diff --git a/packages/walkthrough/steps/15/README.md b/packages/walkthrough/steps/15/README.md
@@ -162,9 +162,9 @@ We have now moved everything out of the app view and controller. The app control
 
 ***
 
-**Next:** [Step 16: Dialogs and Fragments](../16/README.md "In this step, we will take a closer look at another element which can be used to assemble views: the fragment.")
+**Next:** [Step 16: Dialogs and Fragments](../16/README.md)
 
-**Previous:** [Step 14: Margins and Paddings](../14/README.md "Sometimes we need to define some more fine-granular layouts and this is when we can use the flexibility of CSS by adding custom style classes to controls and style them as we like.")
+**Previous:** [Step 14: Margins and Paddings](../14/README.md)
 
 ***
-Original file line number
+Diff line change
@@ Expand Up / @@ -215,7 +215,7 @@ server: @@
     ***
-    **Next:** [Step 2: Creating a Model](../02/README.md "In this step, we create a model. It serves as a container for the data your application operates on.")
+    **Next:** [Step 2: Creating a Model](../02/README.md)
     ***
@@ Expand Down @@