From 2acc76671055a82eb38d2652e5398df5870c2d2a Mon Sep 17 00:00:00 2001 From: klaasderks <61226892+kad-derksn@users.noreply.github.com> Date: Tue, 11 Mar 2025 11:44:53 +0100 Subject: [PATCH] Update 01_suitefile.md Typo fix --- website/docs/chapter-02/01_suitefile.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/chapter-02/01_suitefile.md b/website/docs/chapter-02/01_suitefile.md index 816a3ea..de012e0 100644 --- a/website/docs/chapter-02/01_suitefile.md +++ b/website/docs/chapter-02/01_suitefile.md @@ -128,7 +128,7 @@ It allows you to import keywords from external libraries (`Library`) or resource In this section, the suite name, that is normally derived from the file name, can be redefined with the `Name` setting and its documentation can be defined with the `Documentation` setting. -Additional metadata can be defined by multiple `Metadata` entries, which can containd key-value pairs that can be used to store additional information about the suite, like the author, the version, or related requirements of the suite. +Additional metadata can be defined by multiple `Metadata` entries, which can contain key-value pairs that can be used to store additional information about the suite, like the author, the version, or related requirements of the suite. This section can also define keywords called for execution flow control, such as `Suite Setup` and `Suite Teardown`, which are executed before and after the suite's tests run. See [4.1 Setups (Suite, Test|Task, Keyword)](chapter-04/01_setups.md) and [4.2 Teardowns (Suite, Test|Task, Keyword)](chapter-04/02_teardowns.md) for more information.