nixos/nextcloud: apply doc fixes suggested by fabaff

Co-authored-by: Fabian Affolter <mail@fabian-affolter.ch>

nixos/modules/services/web-apps/nextcloud.xml

@@ -96,14 +96,14 @@
       managing its own configuration. The config file lives in the home directory
       of the <literal>nextcloud</literal> user (by default
       <literal>/var/lib/nextcloud/config/config.php</literal>) and is also used to
-      track several states of the application (e.g. whether installed or not).
+      track several states of the application (e.g., whether installed or not).
      </para>
     </formalpara>
     <para>
      All configuration parameters are also stored in
      <filename>/var/lib/nextcloud/config/override.config.php</filename> which is generated by
      the module and linked from the store to ensure that all values from
-     <filename>config.php</filename>can be modified by the module.
+     <filename>config.php</filename> can be modified by the module.
      However <filename>config.php</filename> manages the application's state and shouldn't be
      touched manually because of that.
     </para>
@@ -123,7 +123,7 @@
     <formalpara>
      <title>Multiple version upgrades</title>
      <para>
-      Nextcloud doesn't allow to move more than one major-version forward. If you're e.g. on
+      Nextcloud doesn't allow to move more than one major-version forward. E.g., if you're on
       <literal>v16</literal>, you cannot upgrade to <literal>v18</literal>, you need to upgrade to
       <literal>v17</literal> first. This is ensured automatically as long as the
       <link linkend="opt-system.stateVersion">stateVersion</link> is declared properly. In that case
@@ -152,7 +152,7 @@
      <listitem>
       <para>
        If this occurs on an <emphasis>existing</emphasis> setup, this is most likely because
-       the maintenance-mode is active. It can be deactivated by running
+       the maintenance mode is active. It can be deactivated by running
        <command>nextcloud-occ maintenance:mode --off</command>. It's advisable though to
        check the logs first on why the maintenance mode was activated.
       </para>
@@ -163,7 +163,7 @@
       <para>
        A re-run of the installer can be forced by <emphasis>deleting</emphasis>
        <filename>/var/lib/nextcloud/config/config.php</filename>. This is the only time
-       where this is advisable because the fresh install doesn't have any state that can be lost.
+       advisable because the fresh install doesn't have any state that can be lost.
        In case that doesn't help, an entire re-creation can be forced via
        <command>rm -rf ~nextcloud/</command>.
       </para>