From b4e1e38e1d0cfa339471460126e8a12ee450957f Mon Sep 17 00:00:00 2001
From: Joao Louceiro <89097431+joaoLouceiro@users.noreply.github.com>
Date: Fri, 4 Oct 2024 11:05:43 +0100
Subject: [PATCH] Type in step-6-a-first-opa-test-1b47457.md

---
 docs/03_Get-Started/step-6-a-first-opa-test-1b47457.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/03_Get-Started/step-6-a-first-opa-test-1b47457.md b/docs/03_Get-Started/step-6-a-first-opa-test-1b47457.md
index 861c41a..670d69c 100644
--- a/docs/03_Get-Started/step-6-a-first-opa-test-1b47457.md
+++ b/docs/03_Get-Started/step-6-a-first-opa-test-1b47457.md
@@ -193,7 +193,7 @@ Let’s start with the action `iPressOnMoreData`. We define a `waitFor` statemen
 > ### Note:  
 > The `Press` action depends on the control that it is triggered on and has a default behavior for most UI controls. If you, for example, execute `Press` on a `sap.m.Page`, this will trigger the *Back* button's `Press` event. This behavior can be overridden by passing an ID as argument to the action. For more information, see the [API Reference: `sap.ui.test.actions.Press`](https://ui5.sap.com/#/api/sap.ui.test.actions.Press). 
 
-The assertion `theTableShouldHaveAllEntries` is structured similarly, but it does not trigger an action. Here, we use the `success` function of `waitFor` to assert if our application is in the expected state. This state is defined by the matchers \(in our case we expect that the list contains 23 items by using the `AggregationLengthEquals`. The `success` function does not execute the additional checks that are needed for triggering an action. the liste does not have to be `interactable` to verify that the state of the application is correct..
+The assertion `theTableShouldHaveAllEntries` is structured similarly, but it does not trigger an action. Here, we use the `success` function of `waitFor` to assert if our application is in the expected state. This state is defined by the matchers \(in our case we expect that the list contains 23 items by using the `AggregationLengthEquals`. The `success` function does not execute the additional checks that are needed for triggering an action. The list does not have to be `interactable` to verify that the state of the application is correct.
 
 With this helper object we can simply check the length of the table aggregation `items` to the expected number of items. We have 23 entries in our local mock data that we also use for this integration test. You can see that the number of items is actually hard-coded in the test. So only if the table has exactly 23 items, the matcher is evaluating to `true` and the assertion is passed successfully.