docs(website): Stick to the AE "afterward"

Signed-off-by: Frank Viernau <[email protected]>

website/docs/development.md

@@ -47,7 +47,7 @@ created run configuration to your needs, e.g. by adding an argument and options
 ## Testing
 
 ORT uses [Kotest](https://github.com/kotest/kotest) as the test framework. For running tests and individual test cases
-from the IDE, the [Kotest plugin](https://plugins.jetbrains.com/plugin/14080-kotest) needs to be installed. Afterwards,
+from the IDE, the [Kotest plugin](https://plugins.jetbrains.com/plugin/14080-kotest) needs to be installed. Afterward,
 tests can be run via the green "Play" icon from the gutter as described above.
 
 When running functional tests (for package managers) from the command line, ORT supports the special value "unified" for

website/docs/tools/scanner.md

@@ -6,7 +6,7 @@ sidebar_position: 4
 
 This tool wraps underlying license / copyright scanners with a common API so all supported scanners can be used in the
 same way to easily run them and compare their results. If passed an ORT result file with an analyzer result (`-i`), the
-*scanner* will automatically download the sources of the dependencies via the *downloader* and scan them afterwards.
+*scanner* will automatically download the sources of the dependencies via the *downloader* and scan them afterward.
 
 We recommend to use ORT with any of the following scanners as their integrations have been thoroughly tested (in
 alphabetical order):
@@ -29,7 +29,7 @@ For a comparison of some of these, see this
 In order to not download or scan any previously scanned sources again, or to reuse scan results generated via other
 services, the *scanner* can be configured to use so-called storage backends. Before processing a package, it checks
 whether compatible scan results are already available in one of the storages declared; if this is the case, they
-are fetched and reused. Otherwise, the package's source code is downloaded and scanned. Afterwards, the new scan
+are fetched and reused. Otherwise, the package's source code is downloaded and scanned. Afterward, the new scan
 results can be put into a storage for later reuse.
 
 This reuse of scan results can actually happen on a per-repository (`type: "PROVENANCE_BASED"`) or per-package