[tor-commits] [community/master] Clean up a few phrases

[gus at torproject.org]

commit 45ac51b0e3d00b456604123885a7b6f1ff6af646
Author: null pointer exception <57326449+deathgrippin at users.noreply.github.com>
Date:   Fri Jun 5 19:06:53 2020 +0000

    Clean up a few phrases
    
    - Change language from "onion service version X" to "vX onion service" to fit in with other pages
    - Reword a few phrases to make them less awkward to read
    - Add missing spaces and colons
---
 content/onion-services/advanced/client-auth/contents.lr | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/content/onion-services/advanced/client-auth/contents.lr b/content/onion-services/advanced/client-auth/contents.lr
index 18be426..24cb573 100644
--- a/content/onion-services/advanced/client-auth/contents.lr
+++ b/content/onion-services/advanced/client-auth/contents.lr
@@ -18,13 +18,13 @@ body:
 
 Client authorization is a method to make an onion service private and authenticated.
 It requires Tor clients to provide an authentication credential in order to connect to the onion service.
-In Onion services version 3, this method works with a pair of keys (a public and a private).
+For v3 onion services, this method works with a pair of keys (a public and a private).
 The service side is configured with a public key and the client can only access it with a private key.
 
 **Note:** Once you have configured client authorization, anyone with the address will not be able to access it from this point on.
 If no authorization is configured, the service will be accessible to anyone with the onion address.
 
-## Configuring Onion service version 3
+## Configuring v3 Onion Services
 
 ### Service side
 
@@ -59,16 +59,16 @@ $ openssl pkey -in /tmp/k1.prv.pem -pubout | grep -v " PUBLIC KEY" | base64pem -
 
      $ cat /tmp/k1.pub.key
 
-**Step 4.** Create an authorized client file
+**Step 4.** Create an authorized client file:
 
 Format the client authentication and create a new file in `<HiddenServiceDir>/authorized_clients/` directory.
 Each file in that directory should be suffixed with ".auth" (i.e. "alice.auth"; the file name is irrelevant) and its content format must be:
 
      <auth-type>:<key-type>:<base32-encoded-public-key>
 
-The supported `<auth-type>` are: "descriptor".
+The supported values for `<auth-type>` are: "descriptor".
 
-The supported `<key-type>` are:"x25519".
+The supported values for `<key-type>` are: "x25519".
 
 The `<base32-encoded-public-key>` is the base32 representation of the raw key bytes only (32 bytes for x25519).
 
@@ -78,7 +78,7 @@ For example, the file `/var/lib/tor/hidden_service/authorized_clients/alice.auth
 
 If you are planning to have more authenticated clients, each file must contain one line only. Any malformed file will be ignored.
 
-**Step 5.** Restart the tor service
+**Step 5.** Restart the tor service:
 
      $ sudo systemctl reload tor
 
@@ -109,7 +109,7 @@ If you are generating a private key for an onion site, the user does not necessa
 
 For more information about client authentication, please see [Tor manual](https://2019.www.torproject.org/docs/tor-onion-service.html.en#ClientAuthorization).
 
-## Configuring Onion service version 2
+## Configuring v2 Onion Services
 
 To set up Cookie Authentication for **v2** services, see the entries for the [HidServAuth](https://2019.www.torproject.org/docs/tor-manual.html.en#HidServAuth) and [HiddenServiceAuthorizeClient](https://2019.www.torproject.org/docs/tor-manual.html.en#HiddenServiceAuthorizeClient) options in the tor manual.
 First add the following line to the [torrc](https://2019.www.torproject.org/docs/faq.html.en#torrc) file of your onion service:
@@ -122,4 +122,4 @@ To access it with a tor client, add following line to torrc and restart tor:
 
      HidServAuth [onion-address] [auth-cookie] [service-name]
  
-You can connect now to the onion service address.
+You can now connect to the onion service address.