From bd0a7f8322f4543044c7e22d0890a2891e44962f Mon Sep 17 00:00:00 2001 From: Daniel Kahn Gillmor Date: Fri, 20 Feb 2009 15:29:34 -0500 Subject: [PATCH 1/1] more wordsmithing. --- website/advanced-user.mdwn | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/website/advanced-user.mdwn b/website/advanced-user.mdwn index 138fd48..7969018 100644 --- a/website/advanced-user.mdwn +++ b/website/advanced-user.mdwn @@ -105,19 +105,19 @@ Note: Due to a limitation with gnupg, it is not currently possible to limit the domain scope properly, which means that if you fully trust an admin, you'll trust all their certifications. -Because the Monkeysphre relies on GPG's definition of the OpenPGP web -of trust, it is important to understand [how GPG calculates User ID -validity for a key](/trust-models). +Because the Monkeysphere currently relies on GPG's definition of the +OpenPGP web of trust, it is important to understand [how GPG +calculates User ID validity for a key](/trust-models). Miscellaneous ------------- Users can also maintain their own `~/.ssh/authorized_keys` files with -the Monkeysphere. This is primarily useful for accounts on hosts that -are not already systematically using the Monkeysphere for user -authentication. If you're not sure whether this is the case for your -host, ask your system administrator. +the Monkeysphere directly. This is primarily useful for accounts on +hosts that are not already systematically using the Monkeysphere for +user authentication. If you're not sure whether this is the case for +your host, ask your system administrator. If you want to do this as a regular user, use the `update-authorized_keys` command: -- 2.25.1