From bf83926a4659894ed093f61795fc6eb38ca29421 Mon Sep 17 00:00:00 2001
From: Joao Louceiro <89097431+joaoLouceiro@users.noreply.github.com>
Date: Thu, 3 Oct 2024 14:06:42 +0100
Subject: [PATCH] Fix typo 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..5e7cd26 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
@@ -80,7 +80,7 @@ sap.ui.define([
 });
 ```
 
-Let’s add our first new OPA test to the `WorklistJourney.js` file. We describe all test cases related to the worklist logic. We can see that there is already a test `Should see the table with all posts` defined that checks if the table contains the expected number of items. There is a function `opaTest` that initiates a test description and receives a test description as the first argument as well as a callback function as the second argument. This format is similar to the unit test function `QUnit.test` except for the three arguments of the callback function that are specific to OPA.
+Let’s add our first new OPA test to the `WorklistJourney.js` file. We describe all test cases related to the worklist logic. We can see that there is already a test `Should see the table with all posts` defined that checks if the table contains the expected number of items. There is a function `opaTest` that initiates a test and receives a test description as the first argument as well as a callback function as the second argument. This format is similar to the unit test function `QUnit.test` except for the three arguments of the callback function that are specific to OPA.
 
 The three objects `Given`, `When`, `Then` are filled by the OPA runtime when the test is executed and contain the `arrangements`, `actions`, and `assertions` for the test. The "Given-When-Then" pattern is a common style for writing tests in a readable format. To describe a test case, you basically write a user story. Test cases in this format are easy to understand, even by non-technical people.