You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by ch...@apache.org on 2025/05/16 13:23:17 UTC
(yunikorn-site) branch master updated: [YUNIKORN-3079] Fix typos/punctuations in docs (#519)
This is an automated email from the ASF dual-hosted git repository.
chenyulin0719 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/yunikorn-site.git
The following commit(s) were added to refs/heads/master by this push:
new 1a04521fd9 [YUNIKORN-3079] Fix typos/punctuations in docs (#519)
1a04521fd9 is described below
commit 1a04521fd9039502f29e34d1e4ea9dac19a1d974
Author: dmefs <de...@gmail.com>
AuthorDate: Fri May 16 21:21:35 2025 +0800
[YUNIKORN-3079] Fix typos/punctuations in docs (#519)
Closes: #519
Signed-off-by: Yu-Lin Chen <ch...@apache.org>
---
docs/design/cache_removal.md | 2 +-
docs/design/gang_scheduling.md | 4 ++--
docs/user_guide/placement_rules.md | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/design/cache_removal.md b/docs/design/cache_removal.md
index 2312643305..91bd14e8e0 100644
--- a/docs/design/cache_removal.md
+++ b/docs/design/cache_removal.md
@@ -41,7 +41,7 @@ The goal is to provide the same functionality before and after the change.
:::
## Background
-The current Scheduler Core is build up around two major components to store the data: the cache and scheduler objects.
+The current Scheduler Core is built up around two major components to store the data: the cache and scheduler objects.
The cache objects form the base for most data to be tracked.
The Scheduler objects track specific in flight details and are build on top of a cache object.
diff --git a/docs/design/gang_scheduling.md b/docs/design/gang_scheduling.md
index 44560ef11b..d73421e3bd 100644
--- a/docs/design/gang_scheduling.md
+++ b/docs/design/gang_scheduling.md
@@ -60,9 +60,9 @@ Combined flow for the shim and core during startup of an application:
* The placeholder AllocationAsk’s are scheduled by the core as if they were normal AllocationAsk’s. (5)
* All Allocations, even if they are the result of the placeholder AllocationAsks being allocated by the scheduler, are communicated back to the shim.
* The original real pod is passed to the core as an AllocationAsk. (6)
-* After the real pod and all all the placeholder pods are scheduled the shim starts the real pod that triggered the application creation. (7)
+* After the real pod and all the placeholder pods are scheduled the shim starts the real pod that triggered the application creation. (7)
-After the first, real, pod is started the following pods should all be handled in the same way (8):
+After the first real pod is started, the following pods should all be handled in the same way (8):
* A real pod is created on k8s.
* The pod is processed and an AllocationAsk is created.
* The scheduler processes the AllocationAsk (more detail below) and replaces a placeholder with the real allocation.
diff --git a/docs/user_guide/placement_rules.md b/docs/user_guide/placement_rules.md
index 365f13af13..65a7c651a6 100644
--- a/docs/user_guide/placement_rules.md
+++ b/docs/user_guide/placement_rules.md
@@ -67,7 +67,7 @@ A message will be logged about the broken and ignored configuration.
Dots "." in the rule result are replaced by the string "\_dot_".
A dot is replaced because it is used as the hierarchy separator in the fully qualified queue name.
-Replacing the dot occurs before the full queue hierarchy is build and the result is qualified.
+Replacing the dot occurs before the full queue hierarchy is built and the result is qualified.
This means that we allow user name and or tag values to contain dots without the dots affecting the queue hierarchy.
For queues in the configuration that as an example must map to username with a dot you must specify them as follows:
A user rule with the user `user.name` will generate the queue name `root.user_dot_name` as output.
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org