spell-check

policy/tpa-rfc-7-root.md

@@ -18,7 +18,7 @@ There are multiple possible access levels, often conflated:
     their SSH keys authorized to the root user (through Puppet, in the
     `profile::admins::keys` Hiera field)
  2. `sudo` to root: user has access to the `root` user through `sudo`,
-    using their `sudoPassword` defined in LDAP3. Puppet access: by
+    using their `sudoPassword` defined in LDAP. Puppet access: by
     virtue of being able to push to the Puppet git repository, an
     admin necessarily gets `root` access everywhere, because Puppet
     runs as root everywhere
@@ -51,7 +51,7 @@ above.
 
 Another issue that currently happens is the problems service admins
 (which do not have root access) have in managing some services. In
-particular, schleuder and GitLab service admins have had trouble
+particular, Schleuder and GitLab service admins have had trouble
 debugging problems with their service because they do not have the
 necessary access levels to restart their service, edit configuration
 file or install packages.
@@ -99,9 +99,7 @@ How do we grant new users access? Document interop with TPI.
 
 # Examples
 
-Examples:
-
- * dgoulet should have root access on the schleuder server (which
+ * dgoulet should have root access on the Schleuder server (which
    should probably be moved out of `eugeni` beforehand, because we
    probably do not want to grant dgoulet root access on the main mail
    server)
@@ -120,3 +118,7 @@ No deadline set yet.
 
 This proposal is currently in the `draft` state.
 
+<!--  LocalWords:  TPO TPA OpenPGP Hiera LDAP dgoulet GitLab ahf arma
+ -->
+<!--  LocalWords:  Schleuder cryptographic anarcat hiro linus qbi
+ -->