diff --git a/docs/client_handbook/TrueOS Handbook port/trueos_sysadmclient_section.txt b/docs/client_handbook/TrueOS Handbook port/trueos_sysadmclient_section.txt
new file mode 100644
index 0000000..fc42714
--- /dev/null
+++ b/docs/client_handbook/TrueOS Handbook port/trueos_sysadmclient_section.txt	
@@ -0,0 +1,1317 @@
+.. index:: configuration
+.. _SysAdm Client:
+
+SysAdm™ Client
+**************
+
+Beginning with |trueos| 11, most of the system management utilities that
+were previously available in the |pcbsd| Control Panel have been
+rewritten to use the |sysadm| API. This API is designed to make it easy
+to manage any FreeBSD or |trueos| desktop or server system over a secure
+connection from any operating system that has the |sysadm| application
+installed. |sysadm| is built into |trueos|, but downloadable packages
+for other operating systems are available from the
+`SysAdm Website <https://sysadm.us/>`_.
+
+.. note:: By default, |sysadm| does not allow for remote access to the
+   system. Please review the |sysadm| server handbook for instructions
+   on initializing the remote access elements of |sysadm|.
+
+A number of utilities have been removed from Control Panel as they are
+now available in the |sysadm| client:
+
+**Application Management**
+
+* :ref:`AppCafe®`
+
+* :ref:`Update Manager`
+
+**SysAdm Server Settings**
+
+* :ref:`Manage SSL Keys`
+
+**System Management**
+
+* :ref:`Boot Environment Manager`
+
+* :ref:`Task Manager`
+
+* :ref:`User Manager`
+
+**Utilities**
+
+* :ref:`Life Preserver`
+
+The rest of this client guide provides an overview of the |sysadm|
+client and all of its functionality, beginning with |appcafe|.
+
+.. note:: Instructions for using the API in your own scripts can be
+   found in the `SysAdm™ API Reference Guide <http://api.sysadm.us/>`_.
+
+.. index:: software, configuration, sysadm
+.. _AppCafe:
+
+AppCafe®
+========
+
+|appcafe| provides a graphical interface for installing and managing
+FreeBSD packages, which are pre-built applications that have been tested
+for FreeBSD-based operating systems. This interface displays extra
+meta-data, such as application screenshots and lists of similar
+applications.
+
+The rest of this section describes how to manage software using |appcafe|.
+
+.. index:: AppCafe®
+.. _Software Management:
+
+Finding Software
+----------------
+
+The "Browse" tab, shown in
+:numref:`Figure %s: Browse Tab of AppCafe® <appcafe1>`, is used to find
+available software. 
+
+.. _appcafe1:
+
+.. figure:: images/appcafe1.png
+
+This screen contains the following options:
+
+**Back:** click this button to leave a category or search result and
+return to the previous screen.
+
+**Repository drop-down menu:** use this drop-down menu to select the
+repository to search or browse. The selections include: "major"
+(applications available for installation), "base" (applications that
+are part of the base operating system), and "local" (all installed
+applications).
+
+**Search:** to see if an application is available, enter its name and
+click the "binoculars" icon. Alternately, enter a description. For
+example, a search for "browser" will display software with "browser"
+in the name as well as applications which provide browser
+functionality, such as Firefox. 
+
+**Browse Categories:** this drop-down menu lists the available software
+categories. If you select a category, it will only display or show
+search results from that category.
+
+**Popular Searches and Popular Categories:** the buttons in these
+sections can be used to quickly find applications which are recommended
+by other |trueos| users. Click a button to get a curated list of
+applications that match the button's description.
+
+Displayed applications will be listed in alphabetical order.
+Applications which are already installed and which are not required by
+other applications have a trashcan icon which can be clicked to
+uninstall that application. Applications which are not installed have a
+down arrow icon which can be clicked to install that application. 
+
+Click the name of an application to view more information about that
+application. In the example shown in
+:numref:`Figure %s: Viewing the Details of an Installed Application <appcafe2>`,
+the user has clicked :guilabel:`Firefox` on a system that has Firefox
+installed.
+
+.. note:: |appcafe| provides a graphical front-end for displaying the
+   contents of the package database. Since installed applications
+   provide more information to the package database, some fields will
+   be empty, depending upon the  selected repository. For example, the
+   package message will only be displayed when the "local" repository
+   is selected, the package is actually installed, and the package
+   provides a message during installation.
+
+.. _appcafe2:
+
+.. figure:: images/appcafe2.png
+
+As seen in this example, the information for an application includes
+the application's icon, name, and description. Click the application's
+name to open the website for the application in the default web
+browser. If the application is installed, there will be an
+:guilabel:`Uninstall` button.
+
+Beneath this area are 4 tabs. The first tab on the left contains two
+panes. The first (middle) pane displays the package description. The
+second (bottom) pane displays the message that appears when the
+package is installed.
+  
+An example of the "?" tab is shown in 
+:numref:`Figure %s: More Application Details <appcafe3>`
+
+.. _appcafe3:
+
+.. figure:: images/appcafe3.png
+
+This tab displays a variety of information:
+
+* Software version.
+
+* Email address for the maintainer of the FreeBSD port the package is
+  built from.
+
+* The application's architecture. This will indicate the FreeBSD version
+  and whether or not the application is 32-bit or 64-bit. Note |trueos|
+  can run both 32 and 64-bit applications.
+  
+* The application's license.  
+
+* The application's installation size.
+
+* The application's download size.
+
+If the package includes screenshots of the application, you can click
+the next tab, which has an image icon, to view and scroll through the
+screenshots. An example is shown in
+:numref:`Figure %s: Viewing the Application's Screenshots <appcafe4>`
+
+.. _appcafe4:
+
+.. figure:: images/appcafe4.png
+
+An example of the last tab, which has a list icon, is shown in
+:numref:`Figure %s: Viewing the Details of an Installed Application <appcafe5>`.
+
+.. _appcafe5:
+
+.. figure:: images/appcafe5.png
+
+This tab contains the following information. Click the right arrow next
+to an entry to expand its information and the down arrow to collapse
+the information.
+
+* **Build Options:** shows the values of the make options that the
+  package was built with.
+
+* **Dependencies:** lists the dependent packages that this
+  application requires to be installed.
+
+* **Required By:** indicates the names of any other packages that
+  require this software to be installed.
+
+* **Shared Libraries (Required):** lists the names of the libraries
+  that this application requires.
+  
+Managing Installed Software
+---------------------------
+
+To view and manage the applications which are installed on the system,
+click the :guilabel:`Installed` tab.  An example is seen in
+:numref:`Figure %s: Installed Tab of AppCafe® <appcafe6>`.
+
+.. _appcafe6:
+
+.. figure:: images/appcafe6.png
+
+This screen offers several actions:
+
+* **All:** check this box to select all installed applications or
+  uncheck it to deselect all installed applications.
+
+* **Uninstall:** click the garbage can icon to uninstall the selected
+  applications.
+
+* **Clean:** this operation deletes any orphaned packages for the
+  selected applications. An orphaned package is one that is not
+  required by any other applications. It will have a black flag icon
+  (the same as the :guilabel:`Clean` icon) in its :guilabel:`Status`
+  column.
+
+This screen also provides an :guilabel:`Options` drop-down menu which
+allows you to select or deselect a number of options:
+
+* **View All Packages:** by default, the installed tab only shows the
+  packages you installed. Check this box to also see the packages
+  included with the operating system. Packages which have a black banner
+  icon under their :guilabel:`Status` column have dependent packages.
+  This means if you delete a package with a black banner, you will
+  also delete their dependent packages so you are not left with orphaned
+  packages.
+
+* **View Advanced Options:** if you check this box, two extra icons, a
+  lock and an unlock icon, will be added to the right of the trash
+  icon. If you select an application and click the lock icon, a lock
+  lock icon will be added to its :guilabel:`Status` column. As long as
+  an application is locked, it will not be updated by
+  :ref:`Update Manager`. This is useful if you need to remain with a
+  certain version of an application. In order to upgrade an
+  application, you will need to first select it and click the unlock
+  icon.
+
+* **Auto-clean packages:** if you check this box, the :guilabel:`Clean`
+  icon will disappear as you no longer need to manually clean orphans.
+  Instead, whenever you uninstall an application, any orphans will also
+  automatically uninstall.
+
+In the example shown in 
+:numref:`Figure %s: Viewing Applications With All Options Checked <appcafe7>`,
+the user has checked all available options. In this example,
+:guilabel:`aalib` has dependencies (banner icon), :guilabel:`alsa-lib`
+has been locked, and :guilabel:`alsa-plugins` is an orphan (flag icon).
+
+.. _appcafe7:
+
+.. figure:: images/appcafe7.png
+  
+If you install or uninstall any software, click the :guilabel:`Pending`
+tab to view the details of the operation. In the example shown in
+:numref:`Figure %s: Viewing the Status of the Operation <appcafe8>`,
+this system has had a package install and a package locking operation,
+and each has a dated entry in the process log. Highlight an entry and
+check the :guilabel:`View Process Log` box to review the log for the
+operation.
+
+.. _appcafe8:
+
+.. figure:: images/appcafe8.png
+
+.. index:: updates
+.. _Update Manager:
+
+Update Manager
+==============
+
+Update Manager provides a graphical interface for keeping the |trueos|
+operating system and its installed applications up-to-date.
+
+The |trueos| update mechanism provides several safeguards to ensure
+updating the operating system or its software is a low-risk operation.
+The following steps occur automatically during an update:
+
+* The update automatically creates a snapshot (copy) of the current
+  operating system, known as a boot environment (BE), and mounts the
+  snapshot in the background. All of the updates then occur in the
+  snapshot. This means you can safely continue to use your system while
+  it is updating, as no changes are being made to the running version of
+  the operating system or any of the applications currently in use.
+  Instead, all changes are being made to the mounted copy.
+
+.. note:: If the system is getting low on disk space and there is not
+   enough space to create a new BE, the update will fail with a message
+   indicating there is not enough space to perform the update.
+
+* While the update is occurring, and until you reboot after the update,
+  you will be unable to use |appcafe| to manage software. This is a
+  safety measure to prevent package conflicts. Also, the system shutdown
+  and restart buttons will be greyed out until the update is complete
+  and the system is ready to reboot. Should a power failure occur in the
+  middle of an update, the system will reboot into the current boot
+  environment, returning the system to the point before the upgrade
+  started. Simply restart the update to continue the update process.
+
+* Once the update is complete, the new boot environment or updated
+  snapshot is added as the first entry in the boot menu. It is then
+  activated so the system will boot into it, unless you pause the boot
+  menu and specify otherwise. A pop-up message will indicate a reboot is
+  required. You can either finish what you are doing now and reboot into
+  the upgraded snapshot, or ask the system to remind you again later.
+  To configure the time of the next warning, click the
+  :guilabel:`Next Reminder` drop-down menu where you can select 1, 5,
+  12, or 24 hours, 30 minutes, or never (for this login session).
+  Note the system will not apply any more updates, allow you to start
+  another manual update, or install additional software using |appcafe|
+  until you reboot.
+
+* The default ZFS layout used by |trueos| ensures when new boot
+  environments are created, the :file:`/usr/local/`, :file:`/usr/home/`,
+  :file:`/usr/ports/`, :file:`/usr/src/` and :file:`/var/` directories
+  remain untouched. This way, if you decide to roll back to a previous
+  boot environment, you will not lose data in your home directories, any
+  installed applications, or downloaded source files or ports. However,
+  you will return the system to its previous state, before the update
+  was applied.
+
+Managing Updates
+----------------
+
+An example of the :guilabel:`Updates` tab is shown in
+:numref:`Figure %s: Managing Updates <update1>`.
+
+.. _update1:
+
+.. figure:: images/update1.png
+
+In this example, updates are available for installed packages. If a
+security update is available, it will be listed as such. Apply the
+available updates by clicking the box next to each entry you want to
+update, which activates the :guilabel:`Start Updates` button. Once the
+button is pressed, it will change to :guilabel:`Stop Updates` so you can
+stop the update if necessary. As the selected updates are applied, the
+progress of the updates will be displayed.
+
+.. warning:: Update Manager will update **all** installed software. If
+   you have placed a lock on a package using :command:`pkg` or
+   |appcafe|, Update Manager will fail and will generate a message
+   indicating the failure is due to a locked package. If an application
+   is locked and cannot be updated, the software will need to be
+   manually updated instead using :command:`pkg`.
+
+Once the update is complete, Update Manager will provide a message
+indicating a reboot is required. When ready, save your work and manually
+reboot into the new boot environment containing the applied updates.
+
+The :guilabel:`Latest Check` field indicates the date and time the
+system last checked for updates. To manually check for updates, click
+:guilabel:`Check for Updates`.
+
+The :guilabel:`Branches` tab of Update Manager provides a listing of
+available branches. In the example shown in
+:numref:`Figure %s: Switching Branches <update3>`, this system is
+currently running the 10.2 branch and the upcoming 11.0 branch is
+available for selection.
+
+.. _update3:
+
+.. figure:: images/update3.png  
+
+The :guilabel:`Settings` tab is shown in
+:numref:`Figure %s: Settings Tab <update4>`.
+
+.. _update4:
+
+.. figure:: images/update4.png
+
+This tab contains several configurable options:
+
+* **Max Boot Environments:** |trueos| automatically creates a boot
+  environment before updating any software, the operating system, or
+  applying a system update. Once the configured maximum number of boot
+  environments is reached, |trueos| will automatically prune (delete)
+  the oldest automatically created boot environment. However, it will
+  not delete any boot environments created manually using
+  :ref:`Boot Environment Manager`. The default number of boot
+  environments is *5*, with an allowable range from *1* to *10*.
+
+* **Automatically perform updates:** When checked, the automatic
+  updater automatically keeps your system and packages up-to-date.
+  You will know an update has completed when the pop-up menu indicates a
+  reboot is needed to complete the update process. If you uncheck this
+  box, an update will only occur when you choose. You are not required
+  to initiate updates manually. |trueos| uses an automated updater that
+  automatically checks for updates, no more than once per day, 20
+  minutes after a reboot and then every 24 hours.
+
+* **Custom Package Repository:** If you have a custom package
+  repository, check this box. This will activate the :guilabel:`URL`
+  field so you can input the URL to the custom repository.
+
+.. index:: updates
+.. _Upgrading from PC-BSD® 10.x to TrueOS®:
+
+Upgrading from |pcbsd| 10.x to |trueos|
+---------------------------------------
+
+If you are currently using |pcbsd| 10.x, the option to update to
+|trueos| will not appear in the Control Panel version of Update Manager.
+This is because a new installation is required in order to migrate to
+|trueos|. However, the |trueos| installer allows you to keep all your
+existing data and home directories, as it provides the ability to
+install |trueos| into a new boot environment. In other words, the new
+operating system and updated applications are installed while the ZFS
+pool and any existing boot environments are preserved. Since the new
+install is in a boot environment, you retain the option to boot back
+into your previous |pcbsd| installation.
+
+.. note:: This option overwrites the contents of :file:`/etc`. If you
+   have any custom configurations, save them to a backup or your home
+   directory first. Alternately, use :ref:`Boot Environment Manager`
+   post-installation to mount your previous |pcbsd| boot environment to
+   copy over any configuration files you may forget to backup.
+
+To perform the installation to a new boot environment, start the
+TrueOS® installation as described in :ref:`Installing TrueOS®`. In the
+:ref:`System Selection Screen` select to install either a desktop or a
+server. When you press "Next", the pop-up screen shown in
+:numref:`Figure %s: Install to Boot Environment <upgrade1>` will
+appear.
+
+.. _upgrade1:
+
+.. figure:: images/upgrade1.png
+
+To upgrade, select the existing pool to install into and press "OK".
+
+.. warning:: If you instead press "Cancel", the installation will
+   continue as usual and will reformat the disks, destroying any
+   existing data.
+   
+If you press "OK" to proceed with an installation into a new boot
+environment, the installer will skip the "Disk Selection" screen and
+instead show a summary as seen in
+:numref:`Figure %s: Start the Install to Boot Environment <upgrade2>`.
+
+.. _upgrade2:
+
+.. figure:: images/upgrade2.png
+
+Press "Next" to start the installation. Once the installation is
+complete, reboot the system and remove the installation media. The
+post-installation screens will run as described in
+:ref:`Post Installation Configuration and Installation Troubleshooting`
+so that you can configure the new installation.
+
+.. note:: When you get to the :ref:`Create a User Screen`, recreate the
+   primary user account using the same name you used on your PC-BSD®
+   system so that TrueOS® can associate the existing home directory
+   with that user. Once you have logged in, you can use
+   :ref:`User Manager` to recreate any other user accounts or to
+   reassociate any PersonaCrypt accounts.
+
+.. index:: sysadm, configuration
+.. _Manage SSL Keys:
+
+Manage SSL Keys
+===============
+
+.. index:: sysadm, boot environments, ZFS
+.. _Boot Environment Manager:
+
+Boot Environment Manager
+========================
+
+TrueOS® supports a feature of ZFS known as multiple boot environments
+(BEs). With multiple boot environments, the process of updating software
+becomes a low-risk operation as the updates are applied to a different
+boot environment. If needed, you have the option of rebooting into a
+backup boot environment. Other examples of using boot environments
+include: 
+
+* If you are making software changes, you can take a snapshot of that
+  boot environment at any stage during the modifications.
+
+* You can save multiple boot environments on your system and perform
+  various updates on each of them as needed. You can install, test, and
+  update different software packages on each.
+
+* You can mount a boot environment in order to :command:`chroot` into
+  the mount point and update specific packages on the mounted
+  environment.
+
+* You can move a boot environment to another machine, physical or
+  virtual, in order to check hardware support.
+
+.. note:: For boot environments to work properly, 
+   **do not delete the default ZFS mount points during installation.** 
+   The default ZFS layout ensures that when boot environments are
+   created, the :file:`/usr/local/`, :file:`/usr/home/`,
+   :file:`/usr/ports/`, :file:`/usr/src/` and :file:`/var/` directories
+   remain untouched. This way, if you rollback to a previous boot
+   environment, you will not lose data in your home directories, any
+   installed applications, or downloaded src or ports. During
+   installation, you can add additional mount points, just don't delete
+   the default ones.
+
+To ensure that the files that the operating system needs are included
+when the system boots, all boot environments on a TrueOS® system include
+:file:`/usr`, :file:`/usr/local`, and :file:`/var`. User-specific data
+is **not** included in the boot environment. This means that
+:file:`/usr/home`, :file:`/usr/jails`, :file:`/var/log`,
+:file:`/var/tmp`, and :file:`/var/audit` will not change, regardless of
+which boot environment is selected at system boot.
+   
+To view, manage, and create boot environments using the SysAdm™
+graphical client, go to
+:menuselection:`System Management --> Boot Environment Manager`. In the
+example shown in :numref:`Figure %s: Managing Boot Environments <be1>`,
+there is an entry named *initial* that represents the original TrueOS®
+installation.
+
+.. _be1:
+
+.. figure:: images/be1.png
+
+Each entry contains the following information:
+
+* **Name:** the name of the boot entry as it will appear in the boot
+  menu.
+
+* **Nickname:** a description, which can be different from the "Name".
+
+* **Active:** the possible values of this field are "R" (active on
+  reboot), "N" (active now), or "-" (inactive). In this example, the
+  system booted from "initial" and is set to boot from "initial" on
+  the next boot.
+
+* **Space:** the size of the boot environment.
+
+* **Mountpoint:** indicates whether or not the BE is mounted, and if
+  so, where.
+
+* **Date:** the date and time the BE was created.
+  
+From left to right, the buttons on the top bar are used to: 
+
+**Create BE:** creates a new boot environment. You should do this before
+making any changes to the system that may impact on your current boot
+environment. You will be prompted for a name which can only contain
+letters or numbers. Once you click "OK", the system will create the
+environment, then add it to the list of boot environments.
+
+**Clone BE:** creates a copy of the highlighted boot environment.
+
+**Delete BE:** deletes the highlighted boot environment. You can not
+delete the boot environment which is marked as *N* or as
+*R* in the "Active" column.
+
+**Rename BE:** renames the highlighted boot environment. The name is
+what appears in the boot menu when the system boots. You cannot rename
+the BE you are currently booted into.
+
+**Mount BE:** mounts the highlighted BE in :file:`/tmp` so that its
+contents are browseable. Note that this setting only applies to inactive
+BEs.
+
+**Unmount BE:** unmounts the previously mounted BE.
+
+**Activate BE:** tells the system to boot into the highlighted boot
+environment at next system boot. This will change the "Active" column
+to *R*.
+
+If you wish to boot into another boot environment, press :kbd:`7` at
+the :numref:`Figure %s: TrueOS® Boot Menu <install1b>` to access the
+boot menu selection screen. In the example shown in
+:numref:`Figure %s: Boot Environments Menu <be2>`, two boot
+environments are available in the "Boot Environments" section: the
+entry named "initial" represents the initial installation and the
+entry named "mybootenvironment" was manually created using Boot
+Environment Manager. The upper section of this menu indicates that the
+"initial" boot environment is set to active, or the one the system
+has been configured to boot into unless another BE is manually
+selected in this menu. Use the arrow keys to highlight the boot
+environment you would like to boot into, and press :kbd:`Enter` to
+continue booting into the selected boot environment. 
+
+.. _be2:
+
+.. figure:: images/be2.png
+
+.. index:: sysadm, configuration
+.. _Task Manager:
+
+Task Manager
+============
+
+Task Manager provides a graphical view of memory use, per-CPU use and
+a listing of currently running applications. An example is shown in 
+:numref:`Figure %s: Task Manager <task1>`.
+
+.. _task1:
+
+.. figure:: images/task1.png  
+
+The "Running Programs: section provides a graphical front-end to
+`top(1) <https://www.freebsd.org/cgi/man.cgi?query=top>`_.
+
+The "Kill Selected Process" button can be used to terminate the
+selected process.
+
+.. index:: configuration
+.. _User Manager:
+
+User Manager
+============
+
+The TrueOS® User Manager utility allows you to easily add, configure,
+and delete users and groups. To access this utility in SysAdm™, click
+:menuselection:`System Management --> User Manager`. 
+
+In the example shown in
+:numref:`Figure %s: Viewing User Accounts in User Manager <user1>`,
+the system has one user account that was created in the "Create a User
+Screen" during installation.
+
+.. _user1:
+
+.. figure:: images/user1.png
+
+The "Standard" view allows you to configure the following:
+
+* **User Name:** the name the user will use when they log in to the
+  system. It is case sensitive and can not contain any spaces. 
+
+* **Full Name:** this field provides a description of the account and
+  can contain spaces.
+
+* **Password:** this is where you can change the password for the
+  user. The password is case-sensitive and can contain symbols. If you
+  want to display the password as you change it, to make sure you are
+  setting it to the desired value, click the "eye" icon. Click that
+  icon again to show dots in place of the actual password.
+
+* **UID:** this value is greyed out as it is assigned by the operating
+  system and cannot be changed after the user is created.
+
+* **Home Dir Path:** if you change the user's home directory, input the full path
+
+* **Shell Path:** if you change the user's default shell, input the
+  full path to an installed shell. The paths for each installed shell
+  can be found in :file:`/etc/shells`.
+
+If you make any changes to a user's "Details", click the "Save" button
+to save them.
+
+:numref:`Figure %s: Creating a New User Account <user2>` demonstrates
+how this screen changes when you click the "New User" button.
+
+.. _user2:
+
+.. figure:: images/user2.png
+
+Fields outlined in red are required when creating a user. The "User
+Name", "Full Name", and "Password" fields are the same as described in
+the "Details" tab. The rest of the available fields are as follows:
+
+**UID:** by default, the user will be assigned the next available User
+ID (UID). If you need to force a specific UID, uncheck the "Auto" box
+and either input or select the number to use. Note that you cannot use
+an UID that is already in use by another account and those number will
+be appear as red.
+
+**Home Dir Path:** by default, this is set to :file:`/nonexistent`
+which is the correct setting for a system account as it prevents
+unauthorized logins. If you are creating a user account for login
+purposes, input the full path to use for the user's home directory.
+
+**Shell:** by default, this is set to :file:`/usr/bin/nologin` which
+is the correct setting for a system account as it prevents
+unauthorized logins. If you are creating a user account for login
+purposes, input the full path of an installed shell. The paths for
+each installed shell can be found in :file:`/etc/shells`.
+
+**Adminstrator Access:** check this box if the user requires
+`su(1) <https://www.freebsd.org/cgi/man.cgi?query=su>`_ access. Note
+that this setting requires the user to know the password of the *root*
+user.
+
+**Operator Access:** check this box if the user requires
+:command:`sudo` access. This allows the user to precede an
+administrative command with :command:`sudo` and to be prompted for
+their own password.
+
+Once you have made your selections, press the "Save" button to create
+the account.
+
+If you click the "-" (remove) button for a highlighted user, a pop-up
+menu will ask if you are sure that you want to remove the user and a
+second pop-up will ask if you would like to also delete the user's
+home directory (along with all of their files). If you click "No" to
+the second pop-up, the user will still be deleted but their home
+directory will remain. Note that the "-" button will be greyed out if
+you highlight the user that started SysAdm™. It will also be greyed
+out if there is only one user account as you need at least one user to
+be able to login to the TrueOS® system.
+
+If you click the "Advanced View" button, this screen will change to
+show all of the accounts on the system, not just the user accounts 
+that you created. An example is seen in
+:numref:`Figure %s: Viewing All Accounts and Their Details <user3>`. 
+
+.. _user3:
+
+.. figure:: images/user3.png
+
+The accounts that you did not create are known as system accounts and
+are needed by the operating system or installed applications. Do **not**
+delete any accounts that you did not create yourself as doing so may
+cause a previously working application to stop working. "Advanced View"
+provides additional information associated with each account, such as
+the user ID number, full name (description), home directory, default
+shell, and primary group. System accounts usually have a shell of
+*nologin* for security reasons, meaning that an attacker can not try to
+login to the system using that account name.
+
+.. index:: users
+.. _PersonaCrypt:
+
+PersonaCrypt
+------------
+
+TrueOS® provides support for a security feature known as PersonaCrypt.
+A PersonaCrypt device is a removable USB media, such as a USB stick,
+which has been formatted with ZFS and encrypted with GELI. This device
+is used to hold a specific user's home directory, meaning that they
+can securely transport and access their personal files on any TrueOS®
+or PC-BSD® 10.1.2 or higher system. This can be used, for example, to
+securely access one's home directory from a laptop, home computer, and
+work computer. The device is protected by an encryption key and a
+password which is, and should be, separate from the user's login
+password.
+
+.. note:: When a user is configured to use a PersonaCrypt device, that
+   user can not login using an unencrypted session on the same system.
+   In other words, the PersonaCrypt username is reserved for
+   PersonaCrypt use. If you need to login to both encrypted and
+   unencrypted sessions on the same system, create two different user
+   accounts, one for each type of session.
+
+PersonaCrypt uses GELI's ability to split the key into two parts: one
+being your passphrase, and the other being a key stored on disk.
+Without both of these parts, the media cannot be decrypted. This means
+that if somebody steals the key and manages to get your password, it
+is still  worthless without the system it was paired with.
+
+.. warning:: USB devices can and do eventually fail. Always backup any
+   important files stored on the PersonaCrypt device to another device
+   or system.
+
+The "PersonaCrypt" tab can be used to initialize a PersonaCrypt device for any login user, **except** for the currently logged in user. In the
+example shown in
+:numref:`Figure %s: Initialize PersonaCrypt Device <user5>`, a new user,
+named *dlavigne*, has been created and the entry for that user has been
+clicked.
+
+.. _user5: 
+
+.. figure:: images/user5.png
+
+Before a user is configured to use PersonaCrypt on a TrueOS® system, two
+buttons are available in the "PersonaCrypt" section of "Advanced Mode".
+Note that this section is hidden if the currently logged in user is selected. Also, if you have just created a user and do not see these
+options, click "Apply" then re-highlight the user to display these
+options:
+
+* **Initialize Device:** used to prepare the USB device that will be
+  used as the user's home directory.
+
+* **Import Key:** if the user has already created a PersonaCrypt device
+  on another TrueOS® system, click this button to import a previously
+  saved copy of the key associated with the device. Once the key is
+  imported, the user can now login to this computer using PersonaCrypt.
+
+To prepare a PersonaCrypt device for this user, insert a USB stick and
+click "Initialize Device". A pop-up menu will indicate that the current
+contents of the device will be wiped and that the device must be larger
+than the user's current home directory.
+
+.. warning:: since the USB stick will hold the user's home directory and
+   files, ensure that the stick is large enough to meet the anticipated
+   storage needs of the home directory. Since the stick will be
+   reformatted during the initialization process, make sure that any
+   current data on the stick that you need has been copied elsewhere.
+   Also, the faster the stick, the better the user experience while
+   logged in.
+
+Press "OK" in the pop-up menu. This will prompt you to input and confirm
+the password to associate with the device. Another message will ask if
+you are ready. Click "Yes" to initialize the device. The User Manager
+screen will be greyed out while the device is prepared. Once the
+initialization is complete, the User Manager screen will change to
+display the device's key options, as seen in
+:numref:`Figure %s: PersonaCrypt Key Options <user6>`.
+
+.. _user6:
+
+.. figure:: images/user6.png
+
+The following options are now available:
+
+* **Export Key:** used to create a copy of the encryption key so that it
+  can be imported for use on another TrueOS® system.
+
+* **Disable Key (No Data):** used to uninitialize the PersonaCrypt
+  device on this system. Note that the device can still be used to login
+  to other TrueOS® systems.
+
+* **Disable Key (Import Data):** in addition to uninitializing the
+  PersonaCrypt device on this system, copy the contents of the user's
+  home directory to this system.
+
+Once a user has been initialized for PersonaCrypt on the system, their
+user account will no longer be displayed when :ref:`Logging In`
+**unless** their PersonaCrypt device is inserted. Once the USB device is
+inserted, the login screen will add an extra field, as seen in the
+example shown in Figure 4.8b.
+
+.. note:: when stealth sessions have been configured, PersonaCrypt users will still be displayed in the login menu, even if
+   their USB device is not inserted. This is to allow those users the option to instead login using a stealth session.
+
+In the field with the yellow padlock icon, input the password for the
+user account. In the field with the grey USB stick icon, input the
+password associated with the PersonaCrypt device.
+
+.. warning:: To prevent data corruption and freezing the system
+   **DO NOT** remove the PersonaCrypt device while logged in! Always log
+   out of your session before physically removing the device.
+
+.. index:: users
+.. _Managing Groups:
+
+Managing Groups
+---------------
+
+Click the "Groups" tab to view and manage the groups on the system.
+The "Standard" tab, seen in
+:numref:`Figure %s: Managing Groups Using User Manager <user4>`,
+shows the group membership for the *operator* and *wheel* groups:
+
+.. _user4: 
+
+.. figure:: images/user4.png
+
+This screen has 2 columns: 
+
+**Members:** indicates if the highlighted group contains any user
+accounts.
+
+**Available:** shows all of the system and user accounts on the system
+in alphabetical order.
+
+To add an account to a group, highlight the group name, then highlight
+the account name in the "Available" column. Click the left arrow and
+the selected account will appear in the "Members" column. You should
+only add user accounts to groups that you create yourself or when an
+application's installation instructions indicate that an account needs
+to be added to a group.
+
+.. note:: If you add a user to the *operator* group, they will have
+   permission to use commands requiring administrative access and will
+   be prompted for their own password when administrative access is
+   required. If you add a user to the *wheel* group, they will be
+   granted access to the :command:`su` command and will be prompted
+   for the superuser password whenever they use that command.
+
+To view all of the groups on the system, click "Advanced".
+
+.. index:: sysadm, life preserver
+.. _Life Preserver:
+
+Life Preserver
+==============
+
+The Life Preserver utility is designed to take full advantage of the
+functionality provided by ZFS snapshots. This utility allows you to
+schedule snapshots of a ZFS pool and to optionally replicate those
+snapshots to another system over an encrypted connection. This design
+provides several benefits: 
+
+* A snapshot provides a "point-in-time" image of the ZFS pool. In one
+  way, this is similar to a full system backup as the snapshot contains
+  the information for the entire filesystem. However, it has several
+  advantages over a full backup. Snapshots occur instantaneously,
+  meaning that the filesystem does not need to be unmounted and you can
+  continue to use applications on your system as the snapshot is
+  created. Since snapshots contain the meta-data ZFS uses to access
+  files, the snapshots themselves are small and subsequent snapshots
+  only contain the changes that occurred since the last snapshot was
+  taken. This space efficiency means that you can take snapshots often.
+  Snapshots also provide a convenient way to access previous versions of
+  files as you can browse to the point-in-time for the version of the
+  file that you need. Life Preserver makes it easy to configure when
+  snapshots are taken and provides a built-in graphical browser for finding and restoring the files within a snapshot.
+
+* Replication is an efficient way to keep the files on two systems in
+  sync. With Life Preserver, the snapshots taken on the TrueOS® system
+  will be synchronized with their versions stored on the specified
+  backup server.
+
+* Snapshots are sent to the backup server over an encrypted connection.
+
+* Having a copy of the snapshots on another system makes it possible to
+  perform an operating system restore should the TrueOS® system become
+  unusable or to deploy an identical system to different hardware.
+  
+To manage snapshots and replication using the SysAdm™ graphical client,
+go to :menuselection:`Utilities --> Life Preserver`. The rest of this
+section describes where to find and how to use the features built into
+Life Preserver.
+
+.. index:: snapshots, life preserver
+.. _Snapshots Tab:
+
+Snapshots Tab
+-------------
+
+:numref:`Figure %s: Snapshot Tab <lpreserver1>` shows the "Snapshots"
+tab on a system that has not yet been configured. This system has a
+"ZFS Pool" named "tank". 
+
+.. _lpreserver1:
+
+.. figure:: images/lpreserver1.png
+
+This screen will display any created snapshots and provides buttons to:
+
+**Create:** used to create a manual snapshot of the specified pool
+now. For example, you could create a snapshot before making changes to
+an important file, so that you can preserve a copy of the previous
+version of the file. Or, you can create a snapshot as you make
+modifications to the system configuration. When creating a snapshot, a
+pop-up message will prompt you to input a name for the snapshot,
+allowing you to choose a name that is useful in helping you remember
+why you took the snapshot. An entry will be added to this screen for
+the snapshot where the "Name" will be the name you input and the
+"Comment" will inidcate the date and time the snapshot was created.
+
+**Remove:** used to delete a highlighted snapshot. 
+**This is a permanent change that can not be reversed.** In other
+words, the versions of files at that point in time the snapshot was
+created will be lost.
+
+**Revert:** if you highlight a snapshot entry, this button and the
+drop-down menu next to it will activate. You can use the drop-down
+menu to specify which pool or dataset you would like to revert.
+**Be aware that a revert will overwrite the current contents of the selected pool or dataset to the point in time the snapshot was created.**
+This means that files changes that occurred after the snapshot was
+taken will be lost.
+
+.. index:: replication, life preserver
+.. _Replication Tab:
+
+Replication Tab
+---------------
+
+Life Preserver can be configured to replicate snapshots to another
+system over an encrypted SSH connection, though the backup itself is
+stored in an unencrypted format. This ensures that you have a backup
+copy of your snapshots on another system. 
+
+In order to configure replication, the remote system to hold a copy of
+the snapshots must first meet the following requirements:
+
+* The backup server
+  **must be formatted with the latest version of ZFS,** also known as
+  ZFS feature flags or ZFSv5000. Operating systems that support this
+  version of ZFS include TrueOS®, FreeBSD or PC-BSD® 9.2 or higher,
+  and FreeNAS 9.1.x or higher.
+
+* That system must have SSH installed and the SSH service must be
+  running. If the backup server is running TrueOS®, PC-BSD®, FreeNAS®
+  or FreeBSD, SSH is already installed, but you will need to start the
+  SSH service.
+
+* If the backup server is running TrueOS® or PC-BSD®, you will need to
+  open TCP port 22 (SSH) using :ref:`Firewall Manager`. If the server
+  is running FreeBSD and a firewall has been configured, add a rule to
+  open this port in the firewall ruleset. FreeNAS® does not run a
+  firewall by default. Also, if there is a network firewall between
+  the TrueOS® system and the backup system, make sure it has a rule to
+  allow SSH.
+
+:numref:`Figure %s: Replication Tab <lpreserver2>` shows the initial
+"Replication" tab on a system that has not yet been configured for
+replication. This screen is used to create, view, remove, and
+configure the replication schedule.  
+
+.. _lpreserver2:
+
+.. figure:: images/lpreserver2.png
+
+To schedule the replication, click the "+" button to display the
+"Setup Replication" screen shown in
+:numref:`Figure %s: Scheduling a Replication <lpreserver3>`.
+
+.. _lpreserver3:
+
+.. figure:: images/lpreserver3.png
+
+Input the following information:
+
+* **Host IP:** the IP address of the remote system to store the
+  replicated snapshots.
+
+* **SSH Port:** the port number, if the remote system is running SSH
+  on a port other than the default of 22.
+
+* **Dataset:** the name of the ZFS pool and optional dataset on the
+  remote system. For example, "remotetank" will save the snapshots to
+  a ZFS pool of that name and "remotetank/mybackups" will save the
+  snapshots to an existing dataset named "mybackups" on the pool named
+  "remotetank".
+
+* **Frequency:** use the drop-down menu to select how often to
+  initiate the replication. Available choices are "Sync with snapshot"
+  (at the same time a snapshot is created), "Daily" (when selected,
+  displays a time drop-down menu so you can select the time of day),
+  "Hourly", every "30 minutes", every "10 minutes", or "Manual Only"
+  (only occurs when you click the "Start" button) in this screen.
+
+* **Username:** the username must already exist on the remote system,
+  have write access to the specified "Dataset", and have permission to
+  SSH into that system.
+
+* **Password:** the password associated with the "Username".
+
+* **Local DS:** use the drop-down menu to select the pool or dataset
+  to replicate to the remote system.
+
+The buttons at the top of the "Setup Replication" screen are used to:
+
+**+ icon** add a replication schedule. Multiple schedules are
+supported, meaning that you can replicate to multiple systems or
+replicate different "Local DS" datasets at different times.
+
+**- icon** remove an already created, and highlighted, replication
+schedule.
+
+**gear icon:** modify the schedule for the highlighted replication.
+
+**Start:** manually starts a replication to the system specified in
+the highlighted replication.
+
+**Initialize:** deletes the existing replicated snapshots on the
+remote system and starts a new replication. This is useful if a
+replication gets stuck and will not complete.
+
+.. index:: configuration, life preserver
+.. _Schedules Tab:
+
+Schedules Tab
+-------------
+
+This tab is used to manage when snapshots of the ZFS pool are created.
+Multiple snapshot schedules are supported if the system has multiple
+pools.
+
+.. note:: Snapshots are created on the entire pool as they are needed
+   when :ref:`Restoring the Operating System`.
+
+To create a snapshot schedule, click the "camera" icon in the lower
+left corner of this tab. This will activate the "Setup Snapshot
+Schedule" pane as seen in
+:numref:`Figure %s: Scheduling a Snapshot <lpreserver4>`. 
+
+.. _lpreserver4:
+
+.. figure:: images/lpreserver4.png
+
+This pane contains the following options:
+
+**ZPool:** select the ZFS pool to snapshot.
+
+**Snapshots to keep:** snapshots are automatically pruned after the
+specified number of snapshots to prevent snapshots from eventually
+using up all of your disk space. If you would like to have multiple
+versions of files to choose from, select the number of snapshots to
+keep. Note that auto-pruning only occurs on the snapshots generated by
+Life Preserver according to the configured schedule. Auto-pruning will
+not delete any snapshots you create manually in the "Snapshots" tab.
+
+**Frequency:** use the drop-down menu to select how often snapshots
+occur. Options include "Daily" (which will allow you to select the time
+of day), "Hourly" every "30 Minutes", every "10 Minutes", or every "5
+Minutes".
+
+Once you have created a snapshot schedule, you can use the "gear" icon
+next to the "camera" icon to modify the highlighted schedule or the
+"X" icon to delete the highlighted schedule.
+
+This screen can also be used to manage the ZFS scrub schedule. Scrubs
+are recommended as they can provide an early indication of a potential
+disk failure. Since scrubs can be scheduled on a per-pool basis, if you
+have multiple pools, create a scrub schedule for each pool.
+
+To schedule when the scrub occurs, click the third icon from the right
+which will activate the "Setup Scrub Schedule" screen shown in
+:numref:`Figure %s: Scheduling a Scrub <lpreserver5>`. 
+
+.. _lpreserver5:
+
+.. figure:: images/lpreserver5.png
+
+Select the pool from the "ZPool" drop-down menu, then select the
+"Frequency". Supported frequencies are  "Daily", "Weekly", or
+"Monthly". If you select "Daily", you can configure the "Hour". If you
+select "Weekly", you can configure the "Day of week" and the "Hour". If
+you select "Monthly", you can configure the "Date" and "Hour". Since a
+scrub can be disk I/O intensive, it is recommended to pick a time when
+the system will not be in heavy use.
+
+Once you have created a scrub schedule, you can use the "gear" icon
+next to the "schedule scrub" icon to modify the highlighted schedule or
+the "X" icon to delete the highlighted schedule.
+
+.. index:: configuration, life preserver
+.. _Settings Tab:
+
+Settings Tab
+-------------
+
+The "Settings" tab is shown in
+:numref:`Figure %s: Life Preserver Settings <lpreserver6>`. 
+
+.. _lpreserver6:
+
+.. figure:: images/lpreserver6.png
+
+The following settings are configurable:
+
+**Disk Usage Warning:** enter a number up to 99 to indicate at which
+percentage of disk space Life Preserver will display an alert in the
+system tray. This is useful to prevent snapshots from using up all
+available disk space.
+
+**Email:** if you also wish to receive an email when disk usage reaches
+the percentage configured in the "Disk Usage Warning", enter an email
+address.
+
+**Email Trigger:** this setting can be set to "All", "Warn", or "Error"
+and indicates the type of condition that will trigger an email message.
+
+**Recursive Management:**
+
+If you make any changes in this screen, press the "Save Settings"
+button to apply them.
+
+.. index:: backup
+.. _Using the lpreserver CLI:
+
+Using the lpreserver CLI
+------------------------
+
+The :command:`lpreserver` command line utility can also be used to
+manage snapshots and replication. This command needs to be run as the
+superuser. To display its usage, type the command without any arguments:
+
+.. code-block:: none
+
+ lpreserver
+ Life-Preserver 
+ --------------------------------- 
+ Available commands 
+ Type in help <command> for information and usage about that command
+       help - This help file or the help for the specified command
+   cronsnap - Manage scheduled snapshots
+  cronscrub - Manage scheduled scrubs
+   snapshot - Manage snapshot tasks
+  replicate - Manage replication tasks
+        set - Set lpreserver options
+        get - Get list of lpreserver options
+     status - List datasets, along with last snapshot / replication date 
+
+Each command has its own help text that describes its parameters and
+provides a usage example. For example, to receive help on how to use
+the :command:`lpreserver cronsnap` command, type:
+
+.. code-block:: none
+
+ lpreserver help cronsnap
+ Life-Preserver
+ ---------------------------------
+ Help cronsnap
+ Schedule a ZFS snapshot
+ Usage:
+  lpreserver cronsnap <subcommand> <options>
+ Available subcommands:
+        start - Schedule snapshots for a dataset
+         stop - Stop scheduled snapshots for a dataset.
+         list - List scheduled snapshots
+      exclude - Exclude datasets for scheduled snapshots
+    rmexclude - Remove datasets from exclude list for scheduled snapshots
+  listexclude - List excluded datasets for scheduled snapshots
+ start options:
+  start <dataset> <frequency> <numToKeep>
+  frequency = auto / daily@XX / hourly / 30min / 10min / 5min
+                                ^^ Hour to execute
+  numToKeep = Number of snapshots to keep total
+ NOTE: When frequency is set to auto the following will take place:
+  * Snapshots will be created every 5 minutes and kept for an hour.
+  * A hourly snapshot will be kept for a day.
+  * A daily snapshot will be kept for a month.
+  * A Monthly snapshot will be kept for a year.
+  * The life-preserver daemon will also keep track of the zpool disk space,
+    if the capacity falls below 75%, the oldest snapshot will be auto-pruned.
+ Examples:
+  lpreserver cronsnap start tank1/usr/home/kris daily@22 10
+  Schedule snapshots of dataset tank1/usr/home/kris daily at 22:00.
+  10 snapshots will be kept.
+ stop options:
+  stop <dataset>
+ list options:
+  list <dataset>
+  List all snapshot schedules for a dataset.
+  If no dataset is given it will list schedules for all datasets.
+ exclude options:
+  exclude <dataset> <exclude dataset> <exclude dataset> ...
+  Exclude one or more datasets from scheduled snapshots.
+ Examples:
+  lpreserver cronsnap exclude tank1/usr/home/kris tank1/usr/home/kris/tmp tank1/usr/home/kris/test
+  Exclude dataset tank1/usr/home/kris/tmp and tank1/usr/home/kris/test from scheduled snapshots
+  on dataset tank1/usr/home/kris.
+ rmexclude options:
+  rmexclude <dataset> <excluded dataset> <excluded dataset> ...
+  Remove exclude for one or more datasets that was previously excluded from scheduled snapshots.
+  This removes the datasets from the exclude list.
+ Examples:
+  lpreserver cronsnap rmexclude tank1/usr/home/kris tank1/usr/home/kris/tmp tank1/usr/home/kris/test
+  Dataset tank1/usr/home/kris/tmp and tank1/usr/home/kris/test on dataset tank1/usr/home/kris
+  are no longer excluded for scheduled snapshots.
+ listexclude options:
+  listexclude <dataset>
+  List which datasets are excluded from schedule snapshots.
+
+Table 10.10a shows the command line equivalents to the graphical
+options provided by the Life Preserver GUI.
+
+**Table 10.10a: Command Line and GUI Equivalents** 
+
++-------------------+-----------------------------------------------+----------------------------------------------------------------------------------------+
+| **Command Line**  | **GUI**                                       | **Description**                                                                        |
++===================+===============================================+========================================================================================+
+| **cronsnap**      | "Snapshots" tab                               | schedule when snapshots occur and how long to keep them; the **stop** option can be    |
+|                   |                                               | used to disable snapshot creation                                                      |
++-------------------+-----------------------------------------------+----------------------------------------------------------------------------------------+
+| **cronscrub**     | "Schedules" tab                               | schedule a ZFS scrub                                                                   |
++-------------------+-----------------------------------------------+----------------------------------------------------------------------------------------+
+| **get**           | "Settings" tab                                | list Life Preserver options                                                            |
++-------------------+-----------------------------------------------+----------------------------------------------------------------------------------------+
+| **replicate**     | "Replication" tab                             | used to list, add, and remove backup server; read the **help** for this command for    |
+|                   |                                               | examples                                                                               |
++-------------------+-----------------------------------------------+----------------------------------------------------------------------------------------+
+| **set**           | "Settings" tab                                | configures Life Preserver options; read **help** for the list of configurable options  |
++-------------------+-----------------------------------------------+----------------------------------------------------------------------------------------+
+| **snapshot**      | "Snapshots" tab                               | create and replicate a new ZFS snapshot; by default, snapshots are recursive, meaning  |
+|                   |                                               | that a snapshot is taken of every dataset within a pool                                |
++-------------------+-----------------------------------------------+----------------------------------------------------------------------------------------+
+| **status**        |                                               | lists the last snapshot name and replication status                                    |
++-------------------+-----------------------------------------------+----------------------------------------------------------------------------------------+
+
+.. _Restoring the Operating System:
+
+Restoring the Operating System
+------------------------------
+
+If you have replicated the system's snapshots to a remote backup
+server, you can use a TrueOS® installation media to perform an
+operating system restore or to clone another system. Start the
+installation as usual until you get to the screen shown in
+:numref:`Figure %s: Selecting to Restore/Clone From Backup <restore1>`. 
+
+.. _restore1: 
+
+.. figure:: images/restore1.png
+
+Before you can perform a restore, the network interface must be
+configured. Click the "network connectivity" icon (second from the
+left) in order to determine if the network connection was
+automatically detected. If it was not, refer to the instructions in
+:ref:`Network Manager` and make sure that networking is working
+before continuing.
+
+Once you are ready, click "Restore from Life-Preserver backup" and the
+"Next" button. This will start the Restore Wizard. In the screen shown
+in
+:numref:`Figure %s: Input the Information for a SSH Restore <restore2>`,
+input the IP address of the backup server and the name of the user
+account used to replicate the snapshots. If the server is listening on
+a non-standard SSH port, change the "SSH port" number. 
+
+.. _restore2: 
+
+.. figure:: images/restore2.png
+
+Click "Next" and the wizard will provide a summary of your selections.
+If correct, click "Finish"; otherwise, click "Back" to correct them.
+
+Once you click "Finish",
+Once the connection to the backup server succeeds, you will be able to select which host to restore. In the example shown in :numref:`Figure %s: Select the Host to Restore <restore4>`,
+only one host has been backed up to the replication server.
+
+.. _restore4:
+
+.. figure:: images/restore4.png
+
+After making your selection, click "Next". The restore wizard will provide a summary of which host it will restore from, the name of the user account
+associated with the replication, and the hostname of the target system. Click "Finish" and the installer will proceed to the :ref:`Disk Selection Screen`. At
+this point, you can click the "Customize" button to customize the disk options. However, in the screen shown in Figure 3.3h, the ZFS datasets will be greyed
+out as they will be recreated from the backup during the restore. Once you are finished with any customizations, click "Next" to perform the restore.
\ No newline at end of file
diff --git a/docs/client_handbook/sysadmclient.rst b/docs/client_handbook/sysadmclient.rst
index e2abf25..70e4a41 100644
--- a/docs/client_handbook/sysadmclient.rst
+++ b/docs/client_handbook/sysadmclient.rst
@@ -4,21 +4,21 @@
 SysAdm™ Client
 **************
 
-Beginning with TrueOS® 11, most of the system management utilities that
-were previously available in the PC-BSD® Control Panel have been
-rewritten to use the SysAdm™ API. This API is designed to make it easy
-to manage any FreeBSD or TrueOS® desktop or server system over a secure
-connection from any operating system that has the SysAdm™ application
-installed. SysAdm™ is built into TrueOS® and downloadable packages for
-other operating systems are available from the
+Beginning with |trueos| 11, most of the system management utilities that
+were previously available in the |pcbsd| Control Panel have been
+rewritten to use the |sysadm| API. This API is designed to make it easy
+to manage any FreeBSD or |trueos| desktop or server system over a secure
+connection from any operating system that has the |sysadm| application
+installed. |sysadm| is built into |trueos|, but downloadable packages
+for other operating systems are available from the
 `SysAdm Website <https://sysadm.us/>`_.
 
-.. note:: By default, SysAdm™ does not allow for remote access to the
-   system. Please review the SysAdm™ server handbook for instructions
-   on initializing the remote access elements of SysAdm™.
+.. note:: By default, |sysadm| does not allow for remote access to the
+   system. Please review the |sysadm| server handbook for instructions
+   on initializing the remote access elements of |sysadm|.
 
 A number of utilities have been removed from Control Panel as they are
-now available in the SysAdm™ client:
+now available in the |sysadm| client:
 
 **Application Management**
 
@@ -42,8 +42,8 @@ now available in the SysAdm™ client:
 
 * :ref:`Life Preserver`
 
-The rest of this handbook provides an overview of the SysAdm™ client
-and all of its functionality, beginning with AppCafe®.
+The rest of this client guide provides an overview of the |sysadm|
+client and all of its functionality, beginning with |appcafe|.
 
 .. note:: Instructions for using the API in your own scripts can be
    found in the `SysAdm™ API Reference Guide <http://api.sysadm.us/>`_.
@@ -54,13 +54,13 @@ and all of its functionality, beginning with AppCafe®.
 AppCafe®
 ========
 
-AppCafe® provides a graphical interface for installing and managing
+|appcafe| provides a graphical interface for installing and managing
 FreeBSD packages, which are pre-built applications that have been tested
 for FreeBSD-based operating systems. This interface displays extra
 meta-data, such as application screenshots and lists of similar
 applications.
 
-The rest of this section describes how to manage software using AppCafe®.
+The rest of this section describes how to manage software using |appcafe|.
 
 .. index:: AppCafe®
 .. _Software Management:
@@ -99,7 +99,7 @@ search results from that category.
 
 **Popular Searches and Popular Categories:** the buttons in these
 sections can be used to quickly find applications which are recommended
-by other TrueOS® users. Click a button to get a curated list of
+by other |trueos| users. Click a button to get a curated list of
 applications that match the button's description.
 
 Displayed applications will be listed in alphabetical order.
@@ -111,9 +111,10 @@ down arrow icon which can be clicked to install that application.
 Click the name of an application to view more information about that
 application. In the example shown in
 :numref:`Figure %s: Viewing the Details of an Installed Application <appcafe2>`,
-the user has clicked "Firefox" on a system that has Firefox installed.
+the user has clicked :guilabel:`Firefox` on a system that has Firefox
+installed.
 
-.. note:: AppCafe® provides a graphical front-end for displaying the
+.. note:: |appcafe| provides a graphical front-end for displaying the
    contents of the package database. Since installed applications
    provide more information to the package database, some fields will
    be empty, depending upon the  selected repository. For example, the
@@ -128,8 +129,8 @@ the user has clicked "Firefox" on a system that has Firefox installed.
 As seen in this example, the information for an application includes
 the application's icon, name, and description. Click the application's
 name to open the website for the application in the default web
-browser. If the application is installed, there will be an "Uninstall"
-button.
+browser. If the application is installed, there will be an
+:guilabel:`Uninstall` button.
 
 Beneath this area are 4 tabs. The first tab on the left contains two
 panes. The first (middle) pane displays the package description. The
@@ -143,7 +144,7 @@ An example of the "?" tab is shown in
 
 .. figure:: images/appcafe3.png
 
-This tab displays following information:
+This tab displays a variety of information:
 
 * Software version.
 
@@ -151,10 +152,10 @@ This tab displays following information:
   built from.
 
 * The application's architecture. This will indicate the FreeBSD version
-  and whether or not the application is 32-bit or 64-bit. Note that
-  TrueOS® can run both 32- and 64-bit applications.
-  
-* The application's license.  
+  and whether or not the application is 32-bit or 64-bit. Note |trueos|
+  can run both 32 and 64-bit applications.
+
+* The application's license.
 
 * The application's installation size.
 
@@ -196,69 +197,70 @@ Managing Installed Software
 ---------------------------
 
 To view and manage the applications which are installed on the system,
-click the "Installed" tab.  An example is seen in
-:numref:`Figure %s: Installed Tab of AppCafe® <appcafe6>`. 
+click the :guilabel:`Installed` tab.  An example is seen in
+:numref:`Figure %s: Installed Tab of AppCafe® <appcafe6>`.
 
 .. _appcafe6:
 
 .. figure:: images/appcafe6.png
 
-This screen provides the following actions:
+This screen offers several actions:
 
 * **All:** check this box to select all installed applications or
   uncheck it to deselect all installed applications.
-  
+
 * **Uninstall:** click the garbage can icon to uninstall the selected
   applications.
-  
-* **Clean:** this operation deletes any orphaned packages for the 
+
+* **Clean:** this operation deletes any orphaned packages for the
   selected applications. An orphaned package is one that is not
   required by any other applications. It will have a black flag icon
-  (the same as the "Clean" icon) in its "Status" column.
-  
-This screen also provides an "Options" drop-down menu that allows you
-to select or deselect the following options:
+  (the same as the :guilabel:`Clean` icon) in its :guilabel:`Status`
+  column.
+
+This screen also provides an :guilabel:`Options` drop-down menu which
+allows you to select or deselect a number of options:
 
 * **View All Packages:** by default, the installed tab only shows the
-  packages that you installed. Check this box to also see the packages
-  that came with the operating system. Packages which have a black
-  banner icon under their "Status" column have dependent packages.
+  packages you installed. Check this box to also see the packages
+  included with the operating system. Packages which have a black banner
+  icon under their :guilabel:`Status` column have dependent packages.
   This means if you delete a package with a black banner, you will
-  also delete their dependent packages so that you do not end up with
-  orphaned packages.
+  also delete their dependent packages so you are not left with orphaned
+  packages.
 
 * **View Advanced Options:** if you check this box, two extra icons, a
   lock and an unlock icon, will be added to the right of the trash
   icon. If you select an application and click the lock icon, a lock
-  lock icon will be added to its "Status" column. As long as an
-  application is locked, it will not be updated by
-  :ref:`Update Manager`. This can be useful if you need to stay at a
-  certain version of an application. In order to upgrade that
+  lock icon will be added to its :guilabel:`Status` column. As long as
+  an application is locked, it will not be updated by
+  :ref:`Update Manager`. This is useful if you need to remain with a
+  certain version of an application. In order to upgrade an
   application, you will need to first select it and click the unlock
   icon.
 
-* **Auto-clean packages:** if you check this box, the "Clean" icon
-  will disappear as you no longer need to manually clean orphans.
-  Instead, whenever you uninstall an application, any orphans will
-  automatically be uninstalled as well.
+* **Auto-clean packages:** if you check this box, the :guilabel:`Clean`
+  icon will disappear as you no longer need to manually clean orphans.
+  Instead, whenever you uninstall an application, any orphans will also
+  automatically uninstall.
 
 In the example shown in 
 :numref:`Figure %s: Viewing Applications With All Options Checked <appcafe7>`,
-the user has checked all available options. In this example, "aalib"
-has dependencies (banner icon), "alsa-lib" has been locked, and
-"alsa-plugins" is an orphan (flag icon).
+the user has checked all available options. In this example,
+:guilabel:`aalib` has dependencies (banner icon), :guilabel:`alsa-lib`
+has been locked, and :guilabel:`alsa-plugins` is an orphan (flag icon).
 
 .. _appcafe7:
 
 .. figure:: images/appcafe7.png
   
-If you install or uninstall any software, click the "Pending" tab to
-view the details of the operation. In the example shown in
+If you install or uninstall any software, click the :guilabel:`Pending`
+tab to view the details of the operation. In the example shown in
 :numref:`Figure %s: Viewing the Status of the Operation <appcafe8>`,
 this system has had a package install and a package locking operation,
-and each has a dated entry in the process log. If you highlight an
-entry and check the "View Process Log" box, you can review the log for
-that operation.
+and each has a dated entry in the process log. Highlight an entry and
+check the :guilabel:`View Process Log` box to review the log for the
+operation.
 
 .. _appcafe8:
 
@@ -270,59 +272,60 @@ that operation.
 Update Manager
 ==============
 
-Update Manager provides a graphical interface for keeping the TrueOS®
+Update Manager provides a graphical interface for keeping the |trueos|
 operating system and its installed applications up-to-date.
 
-The TrueOS® update mechanism provides several safeguards to ensure that
+The |trueos| update mechanism provides several safeguards to ensure
 updating the operating system or its software is a low-risk operation.
 The following steps occur automatically during an update:
 
 * The update automatically creates a snapshot (copy) of the current
-  operating system, known as a boot environment (BE), and mounts that
+  operating system, known as a boot environment (BE), and mounts the
   snapshot in the background. All of the updates then occur in the
-  snapshot. This means that you can safely continue to use your system
-  while it is updating as no changes are being made to the running
-  version of the operating system or any of the applications currently
-  in use. Instead, all changes are being made to the mounted copy.
+  snapshot. This means you can safely continue to use your system while
+  it is updating, as no changes are being made to the running version of
+  the operating system or any of the applications currently in use.
+  Instead, all changes are being made to the mounted copy.
 
-.. note:: if the system is getting low on disk space and there is not
+.. note:: If the system is getting low on disk space and there is not
    enough space to create a new BE, the update will fail with a message
-   indicating that there is not enough space to perform the update.
+   indicating there is not enough space to perform the update.
 
 * While the update is occurring, and until you reboot after the update,
-  you will not be able to use AppCafe® to manage software. This is a
+  you will be unable to use |appcafe| to manage software. This is a
   safety measure to prevent package conflicts. Also, the system shutdown
   and restart buttons will be greyed out until the update is complete
-  and the system is ready for reboot. Should a power failure occur in
-  the middle of an update, the system will reboot into the current boot
+  and the system is ready to reboot. Should a power failure occur in the
+  middle of an update, the system will reboot into the current boot
   environment, returning the system to the point before the upgrade
   started. Simply restart the update to continue the update process.
 
-* Once the update is complete, the new boot environment, or updated
-  snapshot, is added as the first entry in the boot menu and activated
-  so that the system will boot into it, unless you pause the boot menu
-  and specify otherwise. A pop-up message will indicate that a reboot is
-  required. You can either finish what you are doing and reboot now into
-  the upgraded snapshot, or ask the system to remind you again at a
-  later time. To configure the time of the next warning, click the "Next
-  Reminder" drop-down menu where you can select 1, 5, 12, or 24 hours,
-  30 minutes, or never (for this login session). Note that the system
-  will not apply any more updates or allow you to start another manual
-  update or install additional software using AppCafe® until you reboot.
-  
-* The default ZFS layout used by TrueOS® ensures that when new boot
+* Once the update is complete, the new boot environment or updated
+  snapshot is added as the first entry in the boot menu. It is then
+  activated so the system will boot into it, unless you pause the boot
+  menu and specify otherwise. A pop-up message will indicate a reboot is
+  required. You can either finish what you are doing now and reboot into
+  the upgraded snapshot, or ask the system to remind you again later.
+  To configure the time of the next warning, click the
+  :guilabel:`Next Reminder` drop-down menu where you can select 1, 5,
+  12, or 24 hours, 30 minutes, or never (for this login session).
+  Note the system will not apply any more updates, allow you to start
+  another manual update, or install additional software using |appcafe|
+  until you reboot.
+
+* The default ZFS layout used by |trueos| ensures when new boot
   environments are created, the :file:`/usr/local/`, :file:`/usr/home/`,
   :file:`/usr/ports/`, :file:`/usr/src/` and :file:`/var/` directories
-  remain untouched. This way, if you decide to rollback to a previous
+  remain untouched. This way, if you decide to roll back to a previous
   boot environment, you will not lose data in your home directories, any
-  installed applications, or downloaded src or ports. However, you will
-  return the system to its previous state, before the update was
-  applied.
+  installed applications, or downloaded source files or ports. However,
+  you will return the system to its previous state, before the update
+  was applied.
 
 Managing Updates
 ----------------
 
-An example of the "Updates" tab is shown in
+An example of the :guilabel:`Updates` tab is shown in
 :numref:`Figure %s: Managing Updates <update1>`.
 
 .. _update1:
@@ -330,131 +333,133 @@ An example of the "Updates" tab is shown in
 .. figure:: images/update1.png
 
 In this example, updates are available for installed packages. If a
-security update is available, it will be listed as such. To apply the
-available updates, click the box next to each entry to update, which
-will activate the "Start Updates" button. Once you click that button,
-it will change to "Stop Updates" so that you can stop the update, if
-needed. As the selected updates are applied, the progress of the
-updates will be displayed.
+security update is available, it will be listed as such. Apply the
+available updates by clicking the box next to each entry you want to
+update, which activates the :guilabel:`Start Updates` button. Once the
+button is pressed, it will change to :guilabel:`Stop Updates` so you can
+stop the update if necessary. As the selected updates are applied, the
+progress of the updates will be displayed.
 
 .. warning:: Update Manager will update **all** installed software. If
    you have placed a lock on a package using :command:`pkg` or
-   AppCafe®, Update Manager will fail and will generate a message
-   indicating that the failure is due to a locked package. If you need
-   to lock certain applications against being updated, you will need
-   to instead manually update software as needed using :command:`pkg`.
+   |appcafe|, Update Manager will fail and will generate a message
+   indicating the failure is due to a locked package. If an application
+   is locked and cannot be updated, the software will need to be
+   manually updated instead using :command:`pkg`.
 
 Once the update is complete, Update Manager will provide a message
-indicating that a reboot is required. Save your work and, when ready,
-manually reboot into the new boot environment containing the applied
-updates.
-   
-The "Latest Check" field indicates the date and time the system last
-checked for updates. To manually check for updates, click the "Check
-for Updates" button.
+indicating a reboot is required. When ready, save your work and manually
+reboot into the new boot environment containing the applied updates.
 
-The "Branches" tab of Update Manager provides a listing of available
-branches. In the example shown in
+The :guilabel:`Latest Check` field indicates the date and time the
+system last checked for updates. To manually check for updates, click
+:guilabel:`Check for Updates`.
+
+The :guilabel:`Branches` tab of Update Manager provides a listing of
+available branches. In the example shown in
 :numref:`Figure %s: Switching Branches <update3>`, this system is
 currently running the 10.2 branch and the upcoming 11.0 branch is
 available for selection.
 
+.. TODO update3.png needs to be added to images file.
+
 .. _update3:
 
 .. figure:: images/update3.png  
 
-The "Settings" tab is shown in
+The :guilabel:`Settings` tab is shown in
 :numref:`Figure %s: Settings Tab <update4>`.
 
 .. _update4:
 
-.. figure:: images/update4.png 
+.. figure:: images/update4.png
 
-This tab contains the following configurable options:
+This tab contains several configurable options:
 
-* **Max Boot Environments:** TrueOS® automatically creates a boot
+* **Max Boot Environments:** |trueos| automatically creates a boot
   environment before updating any software, the operating system, or
   applying a system update. Once the configured maximum number of boot
-  environments is reached, TrueOS® will automatically prune (delete)
+  environments is reached, |trueos| will automatically prune (delete)
   the oldest automatically created boot environment. However, it will
-  not delete any boot environments you create manually using
+  not delete any boot environments created manually using
   :ref:`Boot Environment Manager`. The default number of boot
-  environments is *5* and the allowable range is from *1* to *10*. 
+  environments is *5*, with an allowable range from *1* to *10*.
 
-* **Automatically perform updates:** when checked, the automatic
-  updater will automatically keep your system and packages up-to-date.
-  You will know that an update has completed when the pop-up menu
-  indicates a reboot is needed to complete the update process. If you
-  uncheck this box, an update will only occur when you choose.
-  You are not required to initiate updates manually. TrueOS® uses an
-  automated updater that automatically checks for updates, no more than
-  once per day, 20 minutes after a reboot and then every 24 hours.
-  
-* **Custom Package Repository:** if you have a custom package
-  repository, check this box. This will activate the "URL" field so
-  that you can input the URL to the custom repository.
+* **Automatically perform updates:** When checked, the automatic
+  updater automatically keeps your system and packages up-to-date.
+  You will know an update has completed when the pop-up menu indicates a
+  reboot is needed to complete the update process. If you uncheck this
+  box, an update will only occur when you choose. You are not required
+  to initiate updates manually. |trueos| uses an automated updater that
+  automatically checks for updates, no more than once per day, 20
+  minutes after a reboot and then every 24 hours.
+
+* **Custom Package Repository:** If you have a custom package
+  repository, check this box. This will activate the :guilabel:`URL`
+  field so you can input the URL to the custom repository.
 
 .. index:: updates
 .. _Upgrading from PC-BSD® 10.x to TrueOS®:
 
-Upgrading from PC-BSD® 10.x to TrueOS®
---------------------------------------
+Upgrading from |pcbsd| 10.x to |trueos|
+---------------------------------------
 
-If you are currently running PC-BSD® 10.x, the option to update to
-TrueOS® will not appear in the Control Panel version of Update Manager.
+If you are currently using |pcbsd| 10.x, the option to update to
+|trueos| will not appear in the Control Panel version of Update Manager.
 This is because a new installation is required in order to migrate to
-TrueOS®. However, the TrueOS® installer allows you to keep all of your
-existing data and home directories as it provides the ability to install
-TrueOS® into a new boot environment. In other words, the new operating
-system and updated applications are installed while the ZFS pool and
-any existing boot environments are preserved. Since the new install is
-in a boot environment, you retain the option to boot back into your
-previous PC-BSD® installation.
+|trueos|. However, the |trueos| installer allows you to keep all your
+existing data and home directories, as it provides the ability to
+install |trueos| into a new boot environment. In other words, the new
+operating system and updated applications are installed while the ZFS
+pool and any existing boot environments are preserved. Since the new
+install is in a boot environment, you retain the option to boot back
+into your previous |pcbsd| installation.
 
 .. note:: This option overwrites the contents of :file:`/etc`. If you
    have any custom configurations, save them to a backup or your home
-   directory first. Alternately, you can use
-   :ref:`Boot Environment Manager` post-installation to mount your
-   previous PC-BSD® boot environment to copy over any configuration
-   files you forgot to backup.
+   directory first. Alternately, use :ref:`Boot Environment Manager`
+   post-installation to mount your previous |pcbsd| boot environment to
+   copy over any configuration files you may forget to backup.
 
-To perform the installation to a new boot environment, start the TrueOS®
-installation as described in the
+To perform the installation to a new boot environment, start the
+|trueos| installation as described in the
 `TrueOS® Handbook <https://www.trueos.org/handbook/trueos.html>`_. In
 the `System Selection Screen <https://www.trueos.org/handbook/install.html#system-selection-screen>`_,
-select to install either a desktop or a server. Press :guilabel:`Next`
+choose to install either a desktop or a server. Press :guilabel:`Next`
 to view the pop-up screen shown in
-:numref:`Figure %s: Install to Boot Environment <upgrade1>` will appear.
+:numref:`Figure %s: Install to Boot Environment <upgrade1>`.
 
 .. _upgrade1:
 
 .. figure:: images/upgrade1.png
 
-To upgrade, select the existing pool to install into and press "OK".
+To upgrade, select the existing pool to install into and press
+:guilabel:`OK`.
 
-.. warning:: If you instead press "Cancel", the installation will
-   continue as usual and will reformat the disks, destroying any
+.. warning:: If you instead press :guilabel:`Cancel`, the installation
+   will continue as usual and reformat the disks, destroying any
    existing data.
-   
-If you press "OK" to proceed with an installation into a new boot
-environment, the installer will skip the "Disk Selection" screen and
-instead show a summary as seen in
+
+If you press :guilabel:`OK` to proceed with an installation into a new
+boot environment, the installer will skip the "Disk Selection" screen
+and instead show a summary, seen in
 :numref:`Figure %s: Start the Install to Boot Environment <upgrade2>`.
 
 .. _upgrade2:
 
 .. figure:: images/upgrade2.png
 
-Press "Next" to start the installation. Once the installation is
-complete, reboot the system and remove the installation media. The
+Press :guilabel:`Next` to start the installation. Once the installation
+is complete, reboot the system and remove the installation media. The
 post-installation screens will run as described in the
 `Post Installation Configuration and Installation Troubleshooting <https://www.trueos.org/handbook/postinstall.html>`_
-section of the TrueOS® Handbook so you can configure the new installation.
+section of the |trueos| Handbook so you can configure the new
+installation.
 
 .. note:: When you encounter the
    `Create a User Screen <https://www.trueos.org/handbook/postinstall.html#create-a-user-screen>`_,
    recreate the primary user account using the same name you used on
-   your PC-BSD® system so that TrueOS® can associate the existing home
+   your |pcbsd| system so |trueos| can associate the existing home
    directory with that user. Once you have logged in, you can use
    :ref:`User Manager` to recreate any other user accounts or to
    reassociate any PersonaCrypt accounts.
@@ -471,117 +476,121 @@ Manage SSL Keys
 Boot Environment Manager
 ========================
 
-TrueOS® supports a feature of ZFS known as multiple boot environments
+|trueos| supports a feature of ZFS known as multiple boot environments
 (BEs). With multiple boot environments, the process of updating software
 becomes a low-risk operation as the updates are applied to a different
-boot environment. If needed, you have the option of rebooting into a
-backup boot environment. Other examples of using boot environments
-include: 
+boot environment. If needed, there is an option to reboot into a backup
+boot environment. Other examples of using boot environments include:
 
-* If you are making software changes, you can take a snapshot of that
+* When making software changes, you can take a snapshot of that
   boot environment at any stage during the modifications.
 
-* You can save multiple boot environments on your system and perform
-  various updates on each of them as needed. You can install, test, and
-  update different software packages on each.
+* Save multiple boot environments on your system and perform various
+  updates on each of them as needed. Install, test, and update different
+  software packages on each.
 
-* You can mount a boot environment in order to :command:`chroot` into
-  the mount point and update specific packages on the mounted
-  environment.
+* Mount a boot environment in order to :command:`chroot` into the mount
+  point and update specific packages on the mounted environment.
 
-* You can move a boot environment to another machine, physical or
-  virtual, in order to check hardware support.
+* Move a boot environment to another machine, physical or virtual, in
+  order to check hardware support.
 
 .. note:: For boot environments to work properly, 
    **do not delete the default ZFS mount points during installation.** 
-   The default ZFS layout ensures that when boot environments are
-   created, the :file:`/usr/local/`, :file:`/usr/home/`,
+   The default ZFS layout ensures when boot environments are created,
+   the :file:`/usr/local/`, :file:`/usr/home/`,
    :file:`/usr/ports/`, :file:`/usr/src/` and :file:`/var/` directories
    remain untouched. This way, if you rollback to a previous boot
    environment, you will not lose data in your home directories, any
-   installed applications, or downloaded src or ports. During
+   installed applications, or downloaded source files or ports. During
    installation, you can add additional mount points, just don't delete
    the default ones.
 
-To ensure that the files that the operating system needs are included
-when the system boots, all boot environments on a TrueOS® system include
+To ensure the files the operating system needs are included when the
+system boots, all boot environments on a |trueos| system include
 :file:`/usr`, :file:`/usr/local`, and :file:`/var`. User-specific data
-is **not** included in the boot environment. This means that
+is **not** included in the boot environment. This means
 :file:`/usr/home`, :file:`/usr/jails`, :file:`/var/log`,
 :file:`/var/tmp`, and :file:`/var/audit` will not change, regardless of
 which boot environment is selected at system boot.
-   
-To view, manage, and create boot environments using the SysAdm™
+
+To view, manage, and create boot environments using the |sysadm|
 graphical client, go to
 :menuselection:`System Management --> Boot Environment Manager`. In the
 example shown in :numref:`Figure %s: Managing Boot Environments <be1>`,
-there is an entry named *initial* that represents the original TrueOS®
+there is an entry named *initial* that represents the original |trueos|
 installation.
 
 .. _be1:
 
 .. figure:: images/be1.png
 
-Each entry contains the following information:
+Each entry contains the same information:
 
-* **Name:** the name of the boot entry as it will appear in the boot
+* **Name:** The name of the boot entry as it will appear in the boot
   menu.
 
-* **Nickname:** a description, which can be different from the "Name".
+* **Nickname:** A description, which can be different from the
+  :guilabel:`Name`.
 
-* **Active:** the possible values of this field are "R" (active on
-  reboot), "N" (active now), or "-" (inactive). In this example, the
-  system booted from "initial" and is set to boot from "initial" on
+* **Active:** The possible values of this field are :guilabel:`R`
+  (active on reboot), :guilabel:`N` (active now), or :guilabel:`-`
+  (inactive). In this example, the system booted from
+  :guilabel:`initial` and is set to boot from :guilabel:`initial` on
   the next boot.
 
-* **Space:** the size of the boot environment.
+* **Space:** The size of the boot environment.
 
-* **Mountpoint:** indicates whether or not the BE is mounted, and if
+* **Mountpoint:** Indicates whether or not the BE is mounted, and if
   so, where.
 
-* **Date:** the date and time the BE was created.
-  
-From left to right, the buttons on the top bar are used to: 
+* **Date:** The date and time the BE was created.
 
-**Create BE:** creates a new boot environment. You should do this before
-making any changes to the system that may impact on your current boot
-environment. You will be prompted for a name which can only contain
-letters or numbers. Once you click "OK", the system will create the
-environment, then add it to the list of boot environments.
+From left to right, the buttons on the top bar are used to:
 
-**Clone BE:** creates a copy of the highlighted boot environment.
+**Create BE:** Creates a new boot environment. Do this before making any
+changes to the system that may impact on your current boot environment.
+You will be prompted for a name which can only contain letters or
+numbers. Click :guilabel:`OK` to create the environment, then the system
+will add it to the list of boot environments.
 
-**Delete BE:** deletes the highlighted boot environment. You can not
-delete the boot environment which is marked as *N* or as
-*R* in the "Active" column.
+**Clone BE:** Creates a copy of the highlighted boot environment.
 
-**Rename BE:** renames the highlighted boot environment. The name is
-what appears in the boot menu when the system boots. You cannot rename
-the BE you are currently booted into.
+**Delete BE:** Deletes the highlighted boot environment. You can not
+delete the boot environment which is marked as *N* or as *R* in the
+:guilabel:`Active` column.
 
-**Mount BE:** mounts the highlighted BE in :file:`/tmp` so that its
-contents are browseable. Note that this setting only applies to inactive
-BEs.
+**Rename BE:** Renames the highlighted boot environment. The name will
+appear in the boot menu when the system boots. You cannot rename the BE
+which is currently booted.
 
-**Unmount BE:** unmounts the previously mounted BE.
+**Mount BE:** Mounts the highlighted BE in :file:`/tmp` so its contents
+are browseable. Note this setting only applies to inactive BEs.
 
-**Activate BE:** tells the system to boot into the highlighted boot
-environment at next system boot. This will change the "Active" column
-to *R*.
+**Unmount BE:** Unmounts the previously mounted BE.
 
-If you wish to boot into another boot environment, press :kbd:`7` at
-the :numref:`Figure %s: TrueOS® Boot Menu <install1b>` to access the
-boot menu selection screen. In the example shown in
-:numref:`Figure %s: Boot Environments Menu <be2>`, two boot
-environments are available in the "Boot Environments" section: the
-entry named "initial" represents the initial installation and the
-entry named "mybootenvironment" was manually created using Boot
-Environment Manager. The upper section of this menu indicates that the
-"initial" boot environment is set to active, or the one the system
-has been configured to boot into unless another BE is manually
-selected in this menu. Use the arrow keys to highlight the boot
-environment you would like to boot into, and press :kbd:`Enter` to
-continue booting into the selected boot environment. 
+**Activate BE:** Notifies the system to boot into the highlighted boot
+environment next system boot. This will change the :guilabel:`Active`
+column to *R*.
+
+.. TODO Add/update screenshot install1b - copy/paste commented note to
+   correct place in text.
+   .. _install1b
+
+   .. figure:: images/install1b.png
+
+To boot into another boot environment, press :kbd:`7` at the
+:numref:`Figure %s: TrueOS® Boot Menu <install1b>` to access the boot
+menu selection screen. In the example shown in
+:numref:`Figure %s: Boot Environments Menu <be2>`, two boot environments
+are available in the "Boot Environments" section: the entry named
+"initial" represents the initial installation and the entry named
+"mybootenvironment" was manually created using Boot Environment Manager.
+The upper section of this menu indicates the "initial" boot environment
+is set to active, or the one the system has been configured to boot into
+unless another BE is manually selected in this menu. Use the arrow keys
+to highlight the boot environment you would like to boot into, and press
+:kbd:`Enter` to continue booting into the selected boot environment.
 
 .. _be2:
 
@@ -594,18 +603,18 @@ Task Manager
 ============
 
 Task Manager provides a graphical view of memory use, per-CPU use and
-a listing of currently running applications. An example is shown in 
+a listing of currently running applications. An example is shown in
 :numref:`Figure %s: Task Manager <task1>`.
 
 .. _task1:
 
-.. figure:: images/task1.png  
+.. figure:: images/task1.png
 
 The "Running Programs: section provides a graphical front-end to
 `top(1) <https://www.freebsd.org/cgi/man.cgi?query=top>`_.
 
-The "Kill Selected Process" button can be used to terminate the
-selected process.
+The :guilabel:`Kill Selected Process` button can be used to terminate
+the selected process.
 
 .. index:: configuration
 .. _User Manager:
@@ -613,9 +622,9 @@ selected process.
 User Manager
 ============
 
-The TrueOS® User Manager utility allows you to easily add, configure,
-and delete users and groups. To access this utility in SysAdm™, click
-:menuselection:`System Management --> User Manager`. 
+The |trueos| User Manager utility allows you to easily add, configure,
+and delete users and groups. To access this utility in |sysadm|, click
+:menuselection:`System Management --> User Manager`.
 
 In the example shown in
 :numref:`Figure %s: Viewing User Accounts in User Manager <user1>`,
@@ -626,102 +635,101 @@ Screen" during installation.
 
 .. figure:: images/user1.png
 
-The "Standard" view allows you to configure the following:
+The :guilabel:`Standard` view allows you to configure the following:
 
-* **User Name:** the name the user will use when they log in to the
-  system. It is case sensitive and can not contain any spaces. 
+* **User Name:** The name the user will use when they log in to the
+  system. It is case sensitive and can not contain any spaces.
 
-* **Full Name:** this field provides a description of the account and
+* **Full Name:** This field provides a description of the account and
   can contain spaces.
 
-* **Password:** this is where you can change the password for the
+* **Password:** This is where you can change the password for the
   user. The password is case-sensitive and can contain symbols. If you
-  want to display the password as you change it, to make sure you are
-  setting it to the desired value, click the "eye" icon. Click that
-  icon again to show dots in place of the actual password.
+  want to display the password as you change it, click the
+  :guilabel:`eye` icon. Click the icon again to show dots in place of
+  the actual password.
 
-* **UID:** this value is greyed out as it is assigned by the operating
+* **UID:** This value is greyed out as it is assigned by the operating
   system and cannot be changed after the user is created.
 
-* **Home Dir Path:** if you change the user's home directory, input the
-  full path
+* **Home Dir Path:** If you change the user's home directory, input the
+  full path.
 
-* **Shell Path:** if you change the user's default shell, input the
+* **Shell Path:** If you change the user's default shell, input the
   full path to an installed shell. The paths for each installed shell
   can be found in :file:`/etc/shells`.
 
-If you make any changes to a user's "Details", click the "Save" button
-to save them.
+If you make any changes to a user's "Details", click the
+:guilabel:`Save` button to save them.
 
 :numref:`Figure %s: Creating a New User Account <user2>` demonstrates
-how this screen changes when you click the "New User" button.
+how this screen changes when you click the :guilabel:`New User` button.
 
 .. _user2:
 
 .. figure:: images/user2.png
 
-Fields outlined in red are required when creating a user. The "User
-Name", "Full Name", and "Password" fields are the same as described in
-the "Details" tab. The rest of the available fields are as follows:
+Fields outlined in red are required when creating a user. The
+:guilabel:`User Name`, :guilabel:`Full Name`, and :guilabel:`Password`
+fields are the same as described in the :guilabel:`Details` tab. There
+are several more available fields:
 
-**UID:** by default, the user will be assigned the next available User
-ID (UID). If you need to force a specific UID, uncheck the "Auto" box
-and either input or select the number to use. Note that you cannot use
-an UID that is already in use by another account and those number will
-be appear as red.
+**UID:** By default, the user will be assigned the next available User
+ID (UID). If you need to force a specific UID, uncheck the
+:guilabel:`Auto` box and either input or select the number to use. Note
+you cannot use an UID already in use by another account and those
+numbers will appear as red.
 
-**Home Dir Path:** by default, this is set to :file:`/nonexistent`
+**Home Dir Path:** By default, this is set to :file:`/nonexistent`
 which is the correct setting for a system account as it prevents
 unauthorized logins. If you are creating a user account for login
 purposes, input the full path to use for the user's home directory.
 
-**Shell:** by default, this is set to :file:`/usr/bin/nologin` which
+**Shell:** By default, this is set to :file:`/usr/bin/nologin`, which
 is the correct setting for a system account as it prevents
 unauthorized logins. If you are creating a user account for login
 purposes, input the full path of an installed shell. The paths for
 each installed shell can be found in :file:`/etc/shells`.
 
-**Adminstrator Access:** check this box if the user requires
+**Adminstrator Access:** Check this box if the user requires
 `su(1) <https://www.freebsd.org/cgi/man.cgi?query=su>`_ access. Note
-that this setting requires the user to know the password of the *root*
-user.
+this setting requires the user to know the password of the *root* user.
 
-**Operator Access:** check this box if the user requires
-:command:`sudo` access. This allows the user to precede an
-administrative command with :command:`sudo` and to be prompted for
-their own password.
+**Operator Access:** Check this box if the user requires :command:`sudo`
+access. This allows the user to precede an administrative command with
+:command:`sudo` and be prompted for their own password.
 
-Once you have made your selections, press the "Save" button to create
-the account.
+Once you have made your selections, press :guilabel:`Save` to create the
+account.
 
-If you click the "-" (remove) button for a highlighted user, a pop-up
-menu will ask if you are sure that you want to remove the user and a
-second pop-up will ask if you would like to also delete the user's
-home directory (along with all of their files). If you click "No" to
-the second pop-up, the user will still be deleted but their home
-directory will remain. Note that the "-" button will be greyed out if
-you highlight the user that started SysAdm™. It will also be greyed
-out if there is only one user account as you need at least one user to
-be able to login to the TrueOS® system.
+If you click :guilabel:`-` (remove) for a highlighted user, a pop-up
+menu will ask if you are sure you want to remove the user and a second
+pop-up will ask if you would also like to delete the user's home
+directory (along with all of their files). If you click :guilabel:`No`
+to the second pop-up, the user will still be deleted, but their home
+directory will remain. Note :guilabel:`-` will be greyed out if you
+highlight the user that started |sysadm|. It will also be greyed out if
+there is only one user account, as you need at least one user to login
+to the |trueos| system.
 
-If you click the "Advanced View" button, this screen will change to
-show all of the accounts on the system, not just the user accounts 
-that you created. An example is seen in
-:numref:`Figure %s: Viewing All Accounts and Their Details <user3>`. 
+If you click :guilabel:`Advanced View`, this screen will change to show
+all of the accounts on the system, not just the user accounts you
+created. An example is seen in
+:numref:`Figure %s: Viewing All Accounts and Their Details <user3>`.
 
 .. _user3:
 
 .. figure:: images/user3.png
 
-The accounts that you did not create are known as system accounts and
-are needed by the operating system or installed applications. Do **not**
-delete any accounts that you did not create yourself as doing so may
-cause a previously working application to stop working. "Advanced View"
-provides additional information associated with each account, such as
-the user ID number, full name (description), home directory, default
-shell, and primary group. System accounts usually have a shell of
-*nologin* for security reasons, meaning that an attacker can not try to
-login to the system using that account name.
+The accounts you did not create are known as system accounts and are
+needed by the operating system or installed applications. Do **not**
+delete any accounts you did not create yourself as doing so may cause a
+previously working application to stop working.
+:guilabel:`Advanced View` provides additional information associated
+with each account, such as the user ID number, full name (description),
+home directory, default shell, and primary group. System accounts
+usually have a shell of *nologin* for security reasons, indicating an
+attacker can not login to the system using that account name.
 
 .. index:: users
 .. _PersonaCrypt:
@@ -729,16 +737,15 @@ login to the system using that account name.
 PersonaCrypt
 ------------
 
-TrueOS® provides support for a security feature known as PersonaCrypt.
+|trueos| provides support for a security feature known as PersonaCrypt.
 A PersonaCrypt device is a removable USB media, such as a USB stick,
-which has been formatted with ZFS and encrypted with GELI. This device
-is used to hold a specific user's home directory, meaning that they
-can securely transport and access their personal files on any TrueOS®
-or PC-BSD® 10.1.2 or higher system. This can be used, for example, to
-securely access one's home directory from a laptop, home computer, and
-work computer. The device is protected by an encryption key and a
-password which is, and should be, separate from the user's login
-password.
+formatted with ZFS and encrypted with GELI. This device is used to hold
+a specific user's home directory, meaning they can securely transport
+and access their personal files on any |trueos| or |pcbsd| 10.1.2 or
+higher system. For example, this can be used to securely access one's
+home directory from a laptop, home computer, and work computer. The
+device is protected by an encryption key and a password which is, and
+should be, separate from the user's login password.
 
 .. note:: When a user is configured to use a PersonaCrypt device, that
    user can not login using an unencrypted session on the same system.
@@ -750,79 +757,81 @@ password.
 PersonaCrypt uses GELI's ability to split the key into two parts: one
 being your passphrase, and the other being a key stored on disk.
 Without both of these parts, the media cannot be decrypted. This means
-that if somebody steals the key and manages to get your password, it
-is still  worthless without the system it was paired with.
+if somebody steals the key and manages to get your password, it is still
+worthless without the system it was paired with.
 
-.. warning:: USB devices can and do eventually fail. Always backup any
-   important files stored on the PersonaCrypt device to another device
-   or system.
+.. warning:: USB devices do eventually fail. Always backup any important
+   files stored on the PersonaCrypt device to another device or system.
 
-The "PersonaCrypt" tab can be used to initialize a PersonaCrypt device
-for any login user, **except** for the currently logged in user. In the
-example shown in
+The :guilabel:`PersonaCrypt` tab can be used to initialize a
+PersonaCrypt device for any login user, **except** for the currently
+logged in user. In the example shown in
 :numref:`Figure %s: Initialize PersonaCrypt Device <user5>`, a new user,
-named *dlavigne*, has been created and the entry for that user has been
+named *dlavigne*, has been created and the entry for the user has been
 clicked.
 
+.. TODO Add user5.png to images folder.
+
 .. _user5: 
 
 .. figure:: images/user5.png
 
-Before a user is configured to use PersonaCrypt on a TrueOS® system, two
-buttons are available in the "PersonaCrypt" section of "Advanced Mode".
-Note that this section is hidden if the currently logged in user is
+Before a user is configured to use PersonaCrypt on a |trueos| system,
+two buttons are available in the "PersonaCrypt" section of "Advanced
+Mode". Note this section is hidden if the currently logged in user is
 selected. Also, if you have just created a user and do not see these
-options, click "Apply" then re-highlight the user to display these
-options:
+options, click :guilabel:`Apply` then re-highlight the user to display
+these options:
 
-* **Initialize Device:** used to prepare the USB device that will be
+* **Initialize Device:** Used to prepare the USB device which will be
   used as the user's home directory.
 
-* **Import Key:** if the user has already created a PersonaCrypt device
-  on another TrueOS® system, click this button to import a previously
+* **Import Key:** If the user has already created a PersonaCrypt device
+  on another |trueos| system, click this button to import a previously
   saved copy of the key associated with the device. Once the key is
   imported, the user can now login to this computer using PersonaCrypt.
 
 To prepare a PersonaCrypt device for this user, insert a USB stick and
-click "Initialize Device". A pop-up menu will indicate that the current
-contents of the device will be wiped and that the device must be larger
-than the user's current home directory.
+click :guilabel:`Initialize Device`. A pop-up menu will indicate the
+current contents of the device will be wiped and the device must be
+larger than the user's current home directory.
 
-.. warning:: since the USB stick will hold the user's home directory and
-   files, ensure that the stick is large enough to meet the anticipated
+.. warning:: Since the USB stick will hold the user's home directory and
+   files, ensure the stick is large enough to meet the anticipated
    storage needs of the home directory. Since the stick will be
-   reformatted during the initialization process, make sure that any
-   current data on the stick that you need has been copied elsewhere.
-   Also, the faster the stick, the better the user experience while
-   logged in.
+   reformatted during the initialization process, make sure any current
+   data on the stick you need has been copied elsewhere. Also, the
+   faster the stick, the better the user experience while logged in.
 
-Press "OK" in the pop-up menu. This will prompt you to input and confirm
-the password to associate with the device. Another message will ask if
-you are ready. Click "Yes" to initialize the device. The User Manager
-screen will be greyed out while the device is prepared. Once the
-initialization is complete, the User Manager screen will change to
-display the device's key options, as seen in
+Press :guilabel:`OK` in the pop-up menu. This will prompt you to input
+and confirm the password to associate with the device. Another message
+will ask if you are ready. Click :guilabel:`Yes` to initialize the
+device. The User Manager screen will be greyed out while the device is
+prepared. Once the initialization is complete, the User Manager screen
+will change to display the device's key options, as seen in
 :numref:`Figure %s: PersonaCrypt Key Options <user6>`.
 
+.. TODO Add user6.png to images folder.
+
 .. _user6:
 
 .. figure:: images/user6.png
 
-The following options are now available:
+Several options are now available:
 
-* **Export Key:** used to create a copy of the encryption key so that it
-  can be imported for use on another TrueOS® system.
+* **Export Key:** Used to create a copy of the encryption key so it can
+  be imported for use on another |trueos| system.
 
-* **Disable Key (No Data):** used to uninitialize the PersonaCrypt
-  device on this system. Note that the device can still be used to login
-  to other TrueOS® systems.
+* **Disable Key (No Data):** Used to uninitialize the PersonaCrypt
+  device on this system. Note the device can still be used to login to
+  other |trueos| systems.
 
-* **Disable Key (Import Data):** in addition to uninitializing the
+* **Disable Key (Import Data):** In addition to uninitializing the
   PersonaCrypt device on this system, copy the contents of the user's
   home directory to this system.
 
 Once a user has been initialized for PersonaCrypt on the system, their
-user account will no longer be displayed when logging in **unless**
+user account will no longer be displayed when logging in, **unless**
 their PersonaCrypt device is inserted. Once the USB device is inserted,
 the login screen will add an extra field, as seen in the example shown
 in Figure 4.8b.
@@ -846,8 +855,8 @@ password associated with the PersonaCrypt device.
 Managing Groups
 ---------------
 
-Click the "Groups" tab to view and manage the groups on the system.
-The "Standard" tab, seen in
+Click the :guilabel:`Groups` tab to view and manage the groups on the
+system. The :guilabel:`Standard` tab, seen in
 :numref:`Figure %s: Managing Groups Using User Manager <user4>`,
 shows the group membership for the *operator* and *wheel* groups:
 
@@ -855,29 +864,29 @@ shows the group membership for the *operator* and *wheel* groups:
 
 .. figure:: images/user4.png
 
-This screen has 2 columns: 
+This screen has 2 columns:
 
-**Members:** indicates if the highlighted group contains any user
+**Members:** Indicates if the highlighted group contains any user
 accounts.
 
-**Available:** shows all of the system and user accounts on the system
+**Available:** Shows all of the system and user accounts on the system
 in alphabetical order.
 
 To add an account to a group, highlight the group name, then highlight
-the account name in the "Available" column. Click the left arrow and
-the selected account will appear in the "Members" column. You should
-only add user accounts to groups that you create yourself or when an
-application's installation instructions indicate that an account needs
-to be added to a group.
+the account name in the :guilabel:`Available` column. Click the left
+arrow and the selected account will appear in the :guilabel:`Members`
+column. You should only add user accounts to groups you create yourself
+or when an application's installation instructions indicate an account
+needs to be added to a group.
 
 .. note:: If you add a user to the *operator* group, they will have
    permission to use commands requiring administrative access and will
    be prompted for their own password when administrative access is
    required. If you add a user to the *wheel* group, they will be
    granted access to the :command:`su` command and will be prompted
-   for the superuser password whenever they use that command.
+   for the superuser password whenever they use the command.
 
-To view all of the groups on the system, click "Advanced".
+To view all of the groups on the system, click :guilabel:`Advanced`.
 
 .. index:: sysadm, life preserver
 .. _Life Preserver:
@@ -889,36 +898,36 @@ The Life Preserver utility is designed to take full advantage of the
 functionality provided by ZFS snapshots. This utility allows you to
 schedule snapshots of a ZFS pool and to optionally replicate those
 snapshots to another system over an encrypted connection. This design
-provides several benefits: 
+provides several benefits:
 
 * A snapshot provides a "point-in-time" image of the ZFS pool. In one
   way, this is similar to a full system backup as the snapshot contains
   the information for the entire filesystem. However, it has several
   advantages over a full backup. Snapshots occur instantaneously,
-  meaning that the filesystem does not need to be unmounted and you can
+  meaning the filesystem does not need to be unmounted and you can
   continue to use applications on your system as the snapshot is
   created. Since snapshots contain the meta-data ZFS uses to access
   files, the snapshots themselves are small and subsequent snapshots
   only contain the changes that occurred since the last snapshot was
-  taken. This space efficiency means that you can take snapshots often.
+  taken. This space efficiency means you can take snapshots often.
   Snapshots also provide a convenient way to access previous versions of
   files as you can browse to the point-in-time for the version of the
-  file that you need. Life Preserver makes it easy to configure when
+  file you need. Life Preserver makes it easy to configure when
   snapshots are taken and provides a built-in graphical browser for
   finding and restoring the files within a snapshot.
 
 * Replication is an efficient way to keep the files on two systems in
-  sync. With Life Preserver, the snapshots taken on the TrueOS® system
+  sync. With Life Preserver, the snapshots taken on the |trueos| system
   will be synchronized with their versions stored on the specified
   backup server.
 
 * Snapshots are sent to the backup server over an encrypted connection.
 
 * Having a copy of the snapshots on another system makes it possible to
-  perform an operating system restore should the TrueOS® system become
+  perform an operating system restore should the |trueos| system become
   unusable or to deploy an identical system to different hardware.
-  
-To manage snapshots and replication using the SysAdm™ graphical client,
+
+To manage snapshots and replication using the |sysadm| graphical client,
 go to :menuselection:`Utilities --> Life Preserver`. The rest of this
 section describes where to find and how to use the features built into
 Life Preserver.
@@ -929,9 +938,9 @@ Life Preserver.
 Snapshots Tab
 -------------
 
-:numref:`Figure %s: Snapshot Tab <lpreserver1>` shows the "Snapshots"
-tab on a system that has not yet been configured. This system has a
-"ZFS Pool" named "tank". 
+:numref:`Figure %s: Snapshot Tab <lpreserver1>` shows the
+:guilabel:`Snapshots` tab on a system not yet configured. This system
+has a "ZFS Pool" named "tank".
 
 .. _lpreserver1:
 
@@ -939,29 +948,29 @@ tab on a system that has not yet been configured. This system has a
 
 This screen will display any created snapshots and provides buttons to:
 
-**Create:** used to create a manual snapshot of the specified pool
+**Create:** Used to create a manual snapshot of the specified pool
 now. For example, you could create a snapshot before making changes to
-an important file, so that you can preserve a copy of the previous
-version of the file. Or, you can create a snapshot as you make
-modifications to the system configuration. When creating a snapshot, a
-pop-up message will prompt you to input a name for the snapshot,
-allowing you to choose a name that is useful in helping you remember
-why you took the snapshot. An entry will be added to this screen for
-the snapshot where the "Name" will be the name you input and the
-"Comment" will inidcate the date and time the snapshot was created.
+an important file, so you can preserve a copy of the previous version of
+the file. Or, you can create a snapshot as you make modifications to the
+system configuration. When creating a snapshot, a pop-up message will
+prompt you to input a name for the snapshot, allowing you to choose a
+name that is useful in helping you remember why you took the snapshot.
+An entry will be added to this screen for the snapshot where the
+:guilabel:`Name` will be the name you input and the :guilabel:`Comment`
+will inidcate the date and time the snapshot was created.
 
-**Remove:** used to delete a highlighted snapshot. 
+**Remove:** Used to delete a highlighted snapshot.
 **This is a permanent change that can not be reversed.** In other
-words, the versions of files at that point in time the snapshot was
+words, the versions of files at the point in time the snapshot was
 created will be lost.
 
-**Revert:** if you highlight a snapshot entry, this button and the
+**Revert:** If you highlight a snapshot entry, this button and the
 drop-down menu next to it will activate. You can use the drop-down
 menu to specify which pool or dataset you would like to revert.
 **Be aware that a revert will overwrite the current contents of the
 selected pool or dataset to the point in time the snapshot was created.**
-This means that files changes that occurred after the snapshot was
-taken will be lost.
+This means files changes occurring after the snapshot was taken will be
+lost.
 
 .. index:: replication, life preserver
 .. _Replication Tab:
@@ -971,41 +980,41 @@ Replication Tab
 
 Life Preserver can be configured to replicate snapshots to another
 system over an encrypted SSH connection, though the backup itself is
-stored in an unencrypted format. This ensures that you have a backup
-copy of your snapshots on another system. 
+stored in an unencrypted format. This ensures you have a backup copy of
+your snapshots on another system.
 
 In order to configure replication, the remote system to hold a copy of
-the snapshots must first meet the following requirements:
+the snapshots must first meet several requirements:
 
 * The backup server
   **must be formatted with the latest version of ZFS,** also known as
   ZFS feature flags or ZFSv5000. Operating systems that support this
-  version of ZFS include TrueOS®, FreeBSD or PC-BSD® 9.2 or higher,
+  version of ZFS include |trueos|, FreeBSD or |pcbsd| 9.2 or higher,
   and FreeNAS 9.1.x or higher.
 
-* That system must have SSH installed and the SSH service must be
-  running. If the backup server is running TrueOS®, PC-BSD®, FreeNAS®
+* The system must have SSH installed and the SSH service must be
+  running. If the backup server is running |trueos|, |pcbsd|, |freenas|
   or FreeBSD, SSH is already installed, but you will need to start the
   SSH service.
 
-* If the backup server is running TrueOS® or PC-BSD®, you will need to
+* If the backup server is running |trueos| or |pcbsd|, you will need to
   open TCP port 22 (SSH) using the :guilabel:`Firewall Manager`. If the
   server is running FreeBSD and a firewall has been configured, add a
-  rule to open this port in the firewall ruleset. FreeNAS® does not run
+  rule to open this port in the firewall ruleset. |freenas| does not run
   a firewall by default. Also, if there is a network firewall between
-  the TrueOS® system and the backup system, make sure it has a rule to
+  the |trueos| system and the backup system, make sure it has a rule to
   allow SSH.
 
 :numref:`Figure %s: Replication Tab <lpreserver2>` shows the initial
-"Replication" tab on a system that has not yet been configured for
-replication. This screen is used to create, view, remove, and
-configure the replication schedule.  
+:guilabel:`Replication` tab on a system that has not yet been configured
+for replication. This screen is used to create, view, remove, and
+configure the replication schedule.
 
 .. _lpreserver2:
 
 .. figure:: images/lpreserver2.png
 
-To schedule the replication, click the "+" button to display the
+To schedule the replication, click :guilabel:`+` to display the
 "Setup Replication" screen shown in
 :numref:`Figure %s: Scheduling a Replication <lpreserver3>`.
 
@@ -1015,51 +1024,54 @@ To schedule the replication, click the "+" button to display the
 
 Input the following information:
 
-* **Host IP:** the IP address of the remote system to store the
+* **Host IP:** The IP address of the remote system to store the
   replicated snapshots.
 
-* **SSH Port:** the port number, if the remote system is running SSH
+* **SSH Port:** The port number, if the remote system is running SSH
   on a port other than the default of 22.
 
-* **Dataset:** the name of the ZFS pool and optional dataset on the
+* **Dataset:** The name of the ZFS pool and optional dataset on the
   remote system. For example, "remotetank" will save the snapshots to
   a ZFS pool of that name and "remotetank/mybackups" will save the
   snapshots to an existing dataset named "mybackups" on the pool named
   "remotetank".
 
-* **Frequency:** use the drop-down menu to select how often to
-  initiate the replication. Available choices are "Sync with snapshot"
-  (at the same time a snapshot is created), "Daily" (when selected,
-  displays a time drop-down menu so you can select the time of day),
-  "Hourly", every "30 minutes", every "10 minutes", or "Manual Only"
-  (only occurs when you click the "Start" button) in this screen.
+* **Frequency:** Use the drop-down menu to select how often to
+  initiate the replication. Available choices are
+  :guilabel:`Sync with snapshot` (at the same time a snapshot is
+  created), :guilabel:`Daily` (when selected, displays a time drop-down
+  menu so you can select the time of day), :guilabel:`Hourly`, every
+  :guilabel:`30 minutes`, every :guilabel:`10 minutes`, or
+  :guilabel:`Manual Only` (only occurs when you click :guilabel:`Start`)
+  in this screen.
 
-* **Username:** the username must already exist on the remote system,
+* **Username:** The username must already exist on the remote system,
   have write access to the specified "Dataset", and have permission to
   SSH into that system.
 
-* **Password:** the password associated with the "Username".
+* **Password:** The password associated with the "Username".
 
-* **Local DS:** use the drop-down menu to select the pool or dataset
+* **Local DS:** Use the drop-down menu to select the pool or dataset
   to replicate to the remote system.
 
-The buttons at the top of the "Setup Replication" screen are used to:
+The buttons at the top of the "Setup Replication" screen have several
+uses:
 
-**+ icon** add a replication schedule. Multiple schedules are
-supported, meaning that you can replicate to multiple systems or
-replicate different "Local DS" datasets at different times.
+* **+ icon:** Sdd a replication schedule. Multiple schedules are
+  supported, meaning you can replicate to multiple systems or replicate
+  different "Local DS" datasets at different times.
 
-**- icon** remove an already created, and highlighted, replication
-schedule.
+* **- icon:** Remove an already created, and highlighted, replication
+  schedule.
 
-**gear icon:** modify the schedule for the highlighted replication.
+* **gear icon:** Modify the schedule for the highlighted replication.
 
-**Start:** manually starts a replication to the system specified in
-the highlighted replication.
+* **Start:** Manually starts a replication to the system specified in
+  the highlighted replication.
 
-**Initialize:** deletes the existing replicated snapshots on the
-remote system and starts a new replication. This is useful if a
-replication gets stuck and will not complete.
+* **Initialize:** Deletes the existing replicated snapshots on the
+  remote system and starts a new replication. This is useful if a
+  replication gets stuck and will not complete.
 
 .. index:: configuration, life preserver
 .. _Schedules Tab:
@@ -1074,28 +1086,29 @@ pools.
 .. note:: Snapshots are created on the entire pool as they are needed
    when :ref:`Restoring the Operating System`.
 
-To create a snapshot schedule, click the "camera" icon in the lower
-left corner of this tab. This will activate the "Setup Snapshot
+To create a snapshot schedule, click the :guilabel:`camera` icon in the
+lower left corner of this tab. This will activate the "Setup Snapshot
 Schedule" pane as seen in
-:numref:`Figure %s: Scheduling a Snapshot <lpreserver4>`. 
+:numref:`Figure %s: Scheduling a Snapshot <lpreserver4>`.
 
 .. _lpreserver4:
 
 .. figure:: images/lpreserver4.png
 
-This pane contains the following options:
+This pane contains several options:
 
-**ZPool:** select the ZFS pool to snapshot.
+**ZPool:** Select the ZFS pool to snapshot.
 
-**Snapshots to keep:** snapshots are automatically pruned after the
+**Snapshots to keep:** Snapshots are automatically pruned after the
 specified number of snapshots to prevent snapshots from eventually
 using up all of your disk space. If you would like to have multiple
 versions of files to choose from, select the number of snapshots to
-keep. Note that auto-pruning only occurs on the snapshots generated by
+keep. Note auto-pruning only occurs on the snapshots generated by
 Life Preserver according to the configured schedule. Auto-pruning will
-not delete any snapshots you create manually in the "Snapshots" tab.
+not delete any snapshots you create manually in the
+:guilabel:`Snapshots` tab.
 
-**Frequency:** use the drop-down menu to select how often snapshots
+**Frequency:** Use the drop-down menu to select how often snapshots
 occur. Options include "Daily" (which will allow you to select the time
 of day), "Hourly" every "30 Minutes", every "10 Minutes", or every "5
 Minutes".
@@ -1111,7 +1124,7 @@ have multiple pools, create a scrub schedule for each pool.
 
 To schedule when the scrub occurs, click the third icon from the right
 which will activate the "Setup Scrub Schedule" screen shown in
-:numref:`Figure %s: Scheduling a Scrub <lpreserver5>`. 
+:numref:`Figure %s: Scheduling a Scrub <lpreserver5>`.
 
 .. _lpreserver5:
 
@@ -1135,31 +1148,30 @@ the "X" icon to delete the highlighted schedule.
 Settings Tab
 -------------
 
-The "Settings" tab is shown in
-:numref:`Figure %s: Life Preserver Settings <lpreserver6>`. 
+The :guilabel:`Settings` tab is shown in
+:numref:`Figure %s: Life Preserver Settings <lpreserver6>`.
 
 .. _lpreserver6:
 
 .. figure:: images/lpreserver6.png
 
-The following settings are configurable:
+Many settings are configurable:
 
-**Disk Usage Warning:** enter a number up to 99 to indicate at which
+**Disk Usage Warning:** Enter a number up to 99 to indicate at which
 percentage of disk space Life Preserver will display an alert in the
 system tray. This is useful to prevent snapshots from using up all
 available disk space.
 
-**Email:** if you also wish to receive an email when disk usage reaches
-the percentage configured in the "Disk Usage Warning", enter an email
-address.
+**Email:** To receive an email when disk usage reaches the percentage
+configured in the "Disk Usage Warning", enter an email address.
 
-**Email Trigger:** this setting can be set to "All", "Warn", or "Error"
-and indicates the type of condition that will trigger an email message.
+**Email Trigger:** This setting can be set to "All", "Warn", or "Error"
+and indicates the type of condition which will trigger an email message.
 
 **Recursive Management:**
 
-If you make any changes in this screen, press the "Save Settings"
-button to apply them.
+If you make any changes in this screen, press :guilabel:`Save Settings`
+to apply them.
 
 .. index:: backup
 .. _Using the lpreserver CLI:
@@ -1174,9 +1186,9 @@ superuser. To display its usage, type the command without any arguments:
 .. code-block:: none
 
  lpreserver
- Life-Preserver 
- --------------------------------- 
- Available commands 
+ Life-Preserver
+ ---------------------------------
+ Available commands
  Type in help <command> for information and usage about that command
        help - This help file or the help for the specified command
    cronsnap - Manage scheduled snapshots
@@ -1185,7 +1197,7 @@ superuser. To display its usage, type the command without any arguments:
   replicate - Manage replication tasks
         set - Set lpreserver options
         get - Get list of lpreserver options
-     status - List datasets, along with last snapshot / replication date 
+     status - List datasets, along with last snapshot / replication date
 
 Each command has its own help text that describes its parameters and
 provides a usage example. For example, to receive help on how to use
@@ -1290,55 +1302,58 @@ Restoring the Operating System
 ------------------------------
 
 If you have replicated the system's snapshots to a remote backup
-server, you can use a TrueOS® installation media to perform an
+server, you can use a |trueos| installation media to perform an
 operating system restore or to clone another system. Start the
 installation as usual until you get to the screen shown in
-:numref:`Figure %s: Selecting to Restore/Clone From Backup <restore1>`. 
+:numref:`Figure %s: Selecting to Restore/Clone From Backup <restore1>`.
 
-.. _restore1: 
+.. _restore1:
 
 .. figure:: images/restore1.png
 
 Before you can perform a restore, the network interface must be
-configured. Click the "network connectivity" icon (second from the
-left) in order to determine if the network connection was
-automatically detected. If it was not, refer to the instructions in the
+configured. Click :guilabel:`Network Connectivity` (second icon from the
+left) in order to determine if the network connection was automatically
+detected. If not, refer to the instructions in the
 `Network Manager <https://www.trueos.org/handbook/using.html#network-manager>`_
-section of the TrueOS® handbook and make sure that networking is
+section of the |trueos| handbook and make sure that networking is
 working before continuing.
 
-Once you are ready, click "Restore from Life-Preserver backup" and the
-"Next" button. This will start the Restore Wizard. In the screen shown
-in
+Once you are ready, click :guilabel:`Restore from Life-Preserver backup`
+and :guilabel:`Next`. This will start the Restore Wizard. In the screen
+shown in
 :numref:`Figure %s: Input the Information for a SSH Restore <restore2>`,
 input the IP address of the backup server and the name of the user
 account used to replicate the snapshots. If the server is listening on
-a non-standard SSH port, change the "SSH port" number. 
+a non-standard SSH port, change the "SSH port" number.
 
-.. _restore2: 
+.. _restore2:
 
 .. figure:: images/restore2.png
 
-Click "Next" and the wizard will provide a summary of your selections.
-If correct, click "Finish"; otherwise, click "Back" to correct them.
+Click :guilabel:`Next` and the wizard will provide a summary of your
+selections. If correct, click :guilabel:`Finish`; otherwise, click
+:guilabel:`Back` to correct them.
 
-Once you click "Finish",
 Once the connection to the backup server succeeds, you will be able to
 select which host to restore. In the example shown in
 :numref:`Figure %s: Select the Host to Restore <restore4>`,
 only one host has been backed up to the replication server.
 
+.. TODO Add restore4.png to images folder.
+
 .. _restore4:
 
 .. figure:: images/restore4.png
 
-After making your selection, click "Next". The restore wizard will
-provide a summary of which host it will restore from, the name of the
-user account associated with the replication, and the hostname of the
-target system. Click "Finish" and the installer will proceed to the
+After making your selection, click :guilabel:`Next`. The restore wizard
+will provide a summary of which host it will restore from, the name of
+the user account associated with the replication, and the hostname of
+the target system. Click :guilabel:`Finish` and the installer will
+proceed to the
 `Disk Selection Screen <https://www.trueos.org/handbook/install.html#disk-selection-screen>`_.
-At this point, you can click the "Customize" button to customize the
-disk options. However, in the screen shown in Figure 3.3h, the ZFS
-datasets will be greyed out as they will be recreated from the backup
-during the restore. Once you are finished with any customizations, click
-"Next" to perform the restore.
\ No newline at end of file
+At this point, you can click the :guilabel:`Customize` button to
+customize the disk options. However, in the screen shown in Figure 3.3h,
+the ZFS datasets will be greyed out as they will be recreated from the
+backup during the restore. Once you are finished with any
+customizations, click :guilabel:`Next` to perform the restore.
\ No newline at end of file