From d5eab97bb7cbf84f5c1d40b81d52f03ef0feb431 Mon Sep 17 00:00:00 2001 From: Rodrigo Benenson Date: Mon, 20 Nov 2023 22:52:07 +0100 Subject: [PATCH] Typo fix: scehduling -> scheduling --- www/content/platforms.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/www/content/platforms.md b/www/content/platforms.md index b3a0ddd3e50..419c11e0ce2 100644 --- a/www/content/platforms.md +++ b/www/content/platforms.md @@ -62,7 +62,7 @@ These security guarantees can be relied on because platforms have *exclusive* co ### [Performance benefits](#performance) {#performance} -Many I/O operations can benefit from being run concurrently. Since platforms are in charge of how those I/O operations are implemented, they can also determine how they are scheduled. This means that both applications and packages can describe which operations they want to run concurrently, and then the platform can optimize the scehduling of these operations using its domain-specific knowledge. +Many I/O operations can benefit from being run concurrently. Since platforms are in charge of how those I/O operations are implemented, they can also determine how they are scheduled. This means that both applications and packages can describe which operations they want to run concurrently, and then the platform can optimize the scheduling of these operations using its domain-specific knowledge. For example, a command-line platform might schedule concurrent operations across all available cores (or some lower number specified by a command-line argument). In contrast, a Web server platform might try to balance available cores across multiple request handlers—to prevent undesirable scenarios like one handler getting all the cores (meaning none of the others can progress).