Commit Diff

Commit:
35340c9f1e87672e883da1df0f83a3882ecb94b1
From:
Omar Polo <op@omarpolo.com>
Date:
Message:
typos
Actions:
Patch | Tree
commit - 540d05dedc087b9216350906fa1310a59b6f6f37
commit + 35340c9f1e87672e883da1df0f83a3882ecb94b1
blob - 8a63d46acbaa1667f87469905e9d0510a8be485c
blob + c62fb3ff7677b0030645be569b6d564ba9265b9e
--- site/quickstart.gmi
+++ site/quickstart.gmi
@@ -42,7 +42,7 @@ Generated files:
         ./example.com.key : private key
 ```
 
-Optionally copy ‘example.com.pem’ and ‘example.com.key’ to another location.
+Optionally, move ‘example.com.pem’ and ‘example.com.key’ to another location.
 
 Make sure that the ‘cert’ and ‘key’ options in the configuration file points to these files.
 
@@ -62,10 +62,10 @@ If gmid was installed from your distribution package m
 
 ### A dedicated user
 
-Ideally, gmid should be run with root privileges and to drop privileges to a local user.  This way, the created certificates can be readable only by root.  For example, on GNU/linux systems a ‘gmid’ user can be created with:
+Ideally, gmid should be started with root privileges and drop privileges to a local user.  This way, the created certificates can be readable only by root.  For example, on GNU/linux systems a ‘gmid’ user can be created with:
 
 ```how to create the gmid user
-$ useradd --system --no-create-home -s /bin/nologin -c "gmid Gemini server" gmid
+# useradd --system --no-create-home -s /bin/nologin -c "gmid Gemini server" gmid
 ```
 
 Please consult your OS documentation for more information on the matter.
@@ -88,7 +88,7 @@ It’s a common practice for system daemons to chroot 
 
 A chroot on UNIX-like OS is an operation that changes the “apparent” root directory (i.e. “/”) from the current process and its child.  Think of it like imprisoning a process into a directory and never letting it escape until it terminates.
 
-Using a chroot may complicate the use of CGI scripts, because then all the dependencies of the scripts (like sh, perl, or other libraries) needs to be installed inside the chroot too.  For this very reason gmid supports FastCGI too.
+Using a chroot may complicate the use of CGI scripts, because then all the dependencies of the scripts (like sh, perl, libraries…) need to be installed inside the chroot too.  For this very reason gmid supports FastCGI.
 
 The chroot feature requires a dedicate user, see the previous section.
 
@@ -97,6 +97,8 @@ To chroot gmid inside a directory, use the ‘chroot
 ```how to use the ‘chroot’ option
 # /etc/gmid.conf
 
+user "gmid"
+
 # the given directory, /var/gemini in this case, must exists.
 chroot "/var/gemini"
 ```
blob - 183db26f8b252263ade39f9635e51716193363a1
blob + 3aad5961766a787a23ce264836c95462da205252
--- site/quickstart.html
+++ site/quickstart.html
@@ -1,7 +1,7 @@
 <!doctype html>
 <html lang="en">
   <head>
-    <title>gmid | contrib</title>
+    <title>gmid quickstart</title>
     <meta charset="utf8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
     <style>
@@ -175,7 +175,7 @@ Generated files:
         ./example.com.pem : certificate
         ./example.com.key : private key</pre>
     <p>
-      Optionally copy ‘example.com.pem’ and ‘example.com.key’ to
+      Optionally, move ‘example.com.pem’ and ‘example.com.key’ to
       another location.
     </p>
     <p>
@@ -198,12 +198,12 @@ Generated files:
     </p>
     <h3>A dedicated user</h3>
     <p>
-      Ideally, gmid should be run with root privileges and to drop
+      Ideally, gmid should be started with root privileges and drop
       privileges to a local user.  This way, the created certificates
       can be readable only by root.  For example, on GNU/linux systems
       a ‘gmid’ user can be created with:
     </p>
-    <pre>$ useradd --system --no-create-home -s /bin/nologin -c "gmid Gemini server" gmid</pre>
+    <pre># useradd --system --no-create-home -s /bin/nologin -c "gmid Gemini server" gmid</pre>
     <p>
       Please consult your OS documentation for more information on the
       matter.
@@ -236,9 +236,9 @@ server "example.com" { … }</pre>
     </p>
     <p>
       Using a chroot may complicate the use of CGI scripts, because
-      then all the dependencies of the scripts (like sh, perl, or
-      other libraries) needs to be installed inside the chroot too.
-      For this very reason gmid supports FastCGI too.
+      then all the dependencies of the scripts (like sh, perl,
+      libraries…) need to be installed inside the chroot too.  For
+      this very reason gmid supports FastCGI.
     </p>
     <p>
       The chroot feature requires a dedicate user, see the previous
@@ -250,6 +250,8 @@ server "example.com" { … }</pre>
     </p>
     <pre># /etc/gmid.conf
 
+user "gmid"
+
 # the given directory, /var/gemini in this case, must exists.
 chroot "/var/gemini"</pre>
     <p>