DMB: package set: fix spell check reports

Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>

Author: cpaelzer

docs/.custom_wordlist.txt

@@ -19,6 +19,7 @@ bioinformatics
 blocklisted
 boolean
 bootable
+bootloader
 bootloaders
 bugfix
 bugtracker
@@ -75,10 +76,12 @@ gvfs
 homeserver
 homeservers
 html
+impactful
 Indri
 installability
 interoperate
 IPs
+ISO
 ISOs
 ITPs
 Jackalope

docs/who-makes-ubuntu/councils/dmb-manage-package-sets.md

@@ -51,7 +51,7 @@ seeds and those that are logically defined by their description.
 
 * A {ref}`seeds` based packageset is instead *mostly* defined by what is seeded
   for a particular Ubuntu variant. That is not strictly only and exactly the
-  content of an iso or image, but might also include related supported seeds
+  content of an ISO or image, but might also include related supported seeds
   that represent common use cases that are not default installed.
 
 ### Seed based packageset - why not just generated?
@@ -64,8 +64,9 @@ Such could cases could be:
 
 * Consider to remove a package from a set if is is in the related seed, but so
   central and impactful, that adding it would effectively make the packageset to
-  require core-developer permission level making it too hard to join as an
-  uploader to that set.
+  require core-developer permission level. This not only reduces impact, it also
+  avoids that all package sets are very hard to join as they need core-dev
+  like requirements to join as an uploader.
 
 * Consider to remove a package from a set if it is also claimed by other seeds.
   In that case it often, but not always, is only updated by Ubuntu core-developers.
@@ -78,18 +79,22 @@ If in doubt it is worthwhile to compare a few sets of data to make decisions
 what might need to be added or dropped from a package set. Here an example
 for the ubuntu-server team:
 
-* Current package set `./edit-acl query --series resolute --packageset ubuntu-server`
-* Seeded by checking anything server'ish in [ubuntu seeds](https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/tree/)
-  and [platform seeds](https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/platform/tree/) and what it depends on.
-  Or in the [germinated output](https://ubuntu-archive-team.ubuntu.com/germinate-output/ubuntu.resolute/) for an artifcat you want to check.
-  Yet one has to admit that seeds are hard to read as they are expanded by
-  dependencies and evaluated for various slightly different artifats.
-  Gladly what you need to compare is often nicely approximated by checking what
-  a team with the same purpose is subscribed to. And if they are not subscribed
-  despite being in the germinated seed it would often be a case of overlapping
-  responsibilities that suggest core-developer rights anyway.
-  Therefore consider `curl --silent http://reports.qa.ubuntu.com/m-r-package-team-mapping.json | jq -r '."ubuntu-server"[]'`
-* Out of that in an example of 2025 we generated and discussed [this list](https://lists.ubuntu.com/archives/devel-permissions/2025-September/002906.html)
+* Fetch the current package set like `./edit-acl query --series resolute --packageset ubuntu-server`
+* Look at the seeds
+  * To do so fetch [ubuntu seeds](https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/tree/)
+    and [platform seeds](https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/platform/tree/),
+    to then check for anything related to server.
+  * Or check the [germinated output](https://ubuntu-archive-team.ubuntu.com/germinate-output/ubuntu.resolute/)
+    for an artifact you are interested in.
+  * Yet one has to admit that seeds are hard to read, because they are expanded by
+    dependencies and evaluated for various slightly different artifacts.
+    Gladly what you need to compare, is often nicely approximated by checking what
+    a team with the a related responsibility is subscribed to. And if they are
+    not subscribed despite being in the germinated seed it would often be a case
+    of overlapping responsibilities that suggest core-developer rights anyway.
+    Therefore consider `curl --silent http://reports.qa.ubuntu.com/m-r-package-team-mapping.json | jq -r '."ubuntu-server"[]'`
+    to be the most simple solution.
+* Out of such a three way comparison in an example of 2025 we generated and discussed [this list](https://lists.ubuntu.com/archives/devel-permissions/2025-September/002906.html)
 
 (dmb-modify-packagesets)=
 ## How to modify a Package set
@@ -126,7 +131,7 @@ This is the more common task compared to {ref}`creating a set <dmb-create-packag
     ```
 
   * Sometimes a package or use case is new, but sometimes it is valid for all
-    releases, in that csae the command should be repeated for all supported releases:
+    releases, in that case the command should be repeated for all supported releases:
 
     ```none
     for RELEASE in $(distro-info --supported); do edit-acl ...; done