Removed information about Yast

concepts/snapper-basic-concept.xml

@@ -37,7 +37,7 @@
        </listitem>
       <listitem>
        <para>
-        Thinly provisioned LVM volumes formatted with XFS.
+        Thinly provisioned LVM volumes formatted with XFS and ext4.
        </para>
       </listitem>
     </itemizedlist>
@@ -50,16 +50,14 @@
 
   <section xml:id="snapper-basic-tasks">
     <title>What can &snapper; do?</title>
-    <para>&snapper; has a command-line interface and a &yast; interface.
-      Both the command-line interface and the &yast; interface can be used
-      interchangeably, allowing you to create, delete and compare
-      snapshots, as well as undo changes made between snapshots.</para>
+    <para>&snapper; has a command-line interface that allows you to create,
+     delete and compare snapshots, as well as undo changes made between snapshots.</para>
     <para>
       Using &snapper;, you can perform the following tasks:</para>
       <itemizedlist mark="bullet" spacing="normal">
         <listitem>
          <para>
-          Undo system changes made by <command>zypper</command> and &yast;. <!-- See
+          Undo system changes made by <command>zypper</command>. <!-- See
           <xref linkend="sec-snapper-undo"/> for details.-->
          </para>
         </listitem>
@@ -101,12 +99,11 @@
    <varlistentry>
      <term>Installation snapshots</term>
      <listitem>
-      <para>
-        Whenever one or more packages are installed with &yast; or &zypper;,
-        three snapshots are created:</para>
+    <para>
+        Whenever one or more packages are installed, snapshots are created in this manner:</para>
       <itemizedlist>
         <listitem><para>Snapshot <literal>0 single</literal>
-        is created automatically and always refers to the current system, as 
+        always exists in &snapper;. It always refers to the current system state, as 
         indicated in the <literal>Description</literal> column. This snapshot 
         captures the state of the system right after the installation process 
         has concluded.</para></listitem>
@@ -120,7 +117,7 @@
         It represents the state of the system after all initial setup has been 
         completed.</para></listitem>  
       </itemizedlist>
-      <para>Old snapshots are automatically deleted. By default, the last ten 
+    <para>Old snapshots are automatically deleted. By default, the last ten 
         important snapshots and the last ten <quote>regular</quote> ones 
         (including administration snapshots) are kept. Installation snapshots 
         are enabled by default. To manually disable installation snapshots, uninstall
@@ -131,7 +128,7 @@
      <term>Administration snapshots</term>
      <listitem>
       <para>
-       Whenever you make changes to the system using &zypper; or &yast;, a 
+       Whenever you make changes to the system, a 
        pair of snapshots is created: one prior to the system change 
        (<quote>pre</quote>) and the other one after the system change 
        (<quote>post</quote>). Old snapshots are automatically deleted.
@@ -144,13 +141,13 @@
     <varlistentry>
       <term>Timeline snapshots</term>
    <listitem>
-    <para>
-     A single snapshot is created every hour. Using the &yast; OS installation 
-     method (default), timeline snapshots are enabled, except for the 
-     root file system. You can configure timeline snapshots to be taken 
-     at different intervals: hourly, daily, weekly, monthly and yearly.
-     Old snapshots are automatically deleted. By default, the first snapshot 
-     of the last ten days, months and years is kept. 
+    <para>A single snapshot is created every hour. Timeline snapshots are 
+    enabled by default, except for the root file system. 
+    The default intervals for timeline snapshots are hourly, daily, weekly, 
+    monthly and yearly. To modify these intervals, users must modify 
+    the systemd timers of &snapper; directly, as this cannot be configured within 
+    &snapper; itself. Old snapshots are automatically deleted. By default, the 
+    first snapshot of the last ten days, months and years is kept.
     </para>
    </listitem>
   </varlistentry>
@@ -179,7 +176,7 @@
        Snapshot of a file system <emphasis>before</emphasis> a modification.
        Each <literal>pre</literal> snapshot corresponds to a
        <literal>post</literal> snapshot.
-       For example, this is used for automatic &yast;/&zypper; snapshots.
+       For example, this is used for automatic snapshots.
       </para>
      </listitem>
   </varlistentry>
@@ -191,7 +188,7 @@
        Snapshot of a file system <emphasis>after</emphasis> a modification.
        Each <literal>post</literal> snapshot corresponds to a
        <literal>pre</literal> snapshot.
-       For example, this is used for automatic &yast;/&zypper; snapshots.
+       For example, this is used for automatic snapshots.
       </para>
      </listitem>
   </varlistentry>
@@ -236,7 +233,7 @@
      <para>
       Snapshots always reside on the same partition or subvolume on which the
       snapshot has been taken. It is not possible to store snapshots on a
-      different partition or subvolume.
+      different file system.
      </para>
     </note>
     <para>

concepts/snapper-default-setup.xml

@@ -221,7 +221,7 @@
         When creating a snapshot, no physical data copies are created. A snapshot only consists of 
         pointers to the respective data blocks. As long as the snapshot remains consistent with 
         the current system, it occupies almost no additional disk space (apart from the metadata 
-        it contains). However, if a file is modified on the system, the changed data is recorded
+        it contains). However, if a file is modified on the system, the original data is recorded
         in the snapshot. Over time, as more changes accumulate and the snapshot diverges from 
         the live system, the snapshot's size increases accordingly.</para>
         <para>To prevent disks from running full (and the system becoming inoperable as a result), we