Update bootstrap doc a bit.

docs/bootstrap.md

@@ -4,7 +4,7 @@ When preparing to run a command, Drush works by *bootstrapping* the Drupal envir
 
 For efficiency and convenience, some Drush commands can work without first bootstrapping a Drupal site, or by only partially bootstrapping a site. This is faster than a full bootstrap. It is also a matter of convenience, because some commands are useful even when you don't have a working Drupal site.
 
-Commands may specify their bootstrap level with via an attribute or an annotation. Commands supplied by Drupal modules are always `@bootstrap full`.
+Commands may specify their bootstrap level with via an attribute or an annotation. Commands supplied by Drupal modules are always `full`.
 
 === "PHP8 Attribute"
 
@@ -36,36 +36,36 @@ Prior to bootstrapping, Drush goes through the *preflight* process, where the fo
     1. The site-alias included on the commandline is loaded if present.
     1. The local selected site is determined, if any.
     1. [Dependency injection](dependency-injection.md) is done.
-    1. Global commandfiles are loaded. Commandfiles with a drush.services.yml are loaded later, during `bootstrap @full`. 
+    1. Global commandfiles are loaded. Commandfiles that ship with modules are loaded later, during `bootstrap @full`. 
     1. The command is dispatched via the Symfony Console component.
 
 Bootstrapping is done from a Symfony Console command hook. The different bootstrap levels are described below.
 
-@bootstrap none
+none
 -----------------------
 Only run Drush _preflight_, without considering Drupal at all. Any code that operates on the Drush installation, and not specifically any Drupal directory, should bootstrap to this phase.
 
-@bootstrap root
+root
 ------------------------------
 Set up and test for a valid Drupal root, either through the --root options, or evaluated based on the current working directory. Any code that interacts with an entire Drupal installation, and not a specific site on the Drupal installation should use this bootstrap phase.
 
-@bootstrap site
+site
 ------------------------------
 Set up a Drupal site directory and the correct environment variables to allow Drupal to find the configuration file. If no site is specified with the --uri options, Drush will assume the site is 'default', which mimics Drupal's behaviour.  Note that it is necessary to specify a full URI, e.g. --uri=http://example.com, in order for certain Drush commands and Drupal modules to behave correctly. See the [Drush configuration](using-drush-configuration.md) for more information. Any code that needs to modify or interact with a specific Drupal site's settings.php file should bootstrap to this phase.
 
-@bootstrap configuration
+configuration
 ---------------------------------------
 Load the settings from the Drupal sites directory. This phase is analogous to the DRUPAL\_BOOTSTRAP\_CONFIGURATION bootstrap phase in Drupal itself, and this is also the first step where Drupal specific code is included. This phase is commonly used for code that interacts with the Drupal install API, as both install.php and update.php start at this phase.
 
-@bootstrap database
+database
 ----------------------------------
 Connect to the Drupal database using the database credentials loaded during the previous bootstrap phase. This phase is analogous to the DRUPAL\_BOOTSTRAP\_DATABASE bootstrap phase in Drupal. Any code that needs to interact with the Drupal database API needs to be bootstrapped to at least this phase.
 
-@bootstrap full
+full
 ------------------------------
 Fully initialize Drupal. This is analogous to the DRUPAL\_BOOTSTRAP\_FULL bootstrap phase in Drupal. Any code that interacts with the general Drupal API should be bootstrapped to this phase.
 
-@bootstrap max
+max
 ---------------------
 This is not an actual bootstrap phase. Commands that use the "max" bootstrap level will cause Drush to bootstrap as far as possible, and then run the command regardless of the bootstrap phase that was reached. This is useful for Drush commands that work without a bootstrapped site, but that provide additional information or capabilities in the presence of a bootstrapped site. For example, [`drush status`](commands/core_status.md) will show progressively more information the farther the site bootstraps.