documentation updates

Running_Linux_OSX.md

@@ -2,7 +2,7 @@
 For Linux systems that [support snapd](https://snapcraft.io/docs/installing-snapd), there is currently the option to install Autopsy from the [snap package](#install-autopsy-snap).  Otherwise, when installing on Debian-based Linux or macOS systems, there are three general steps: [installing prerequisites](#installing-prerequisites), [installing The Sleuth Kit](#installing-the-sleuth-kit), and [installing Autopsy](#installing-autopsy) itself.  On macOS, you will want to [setup the JNA paths](#setup-macos-jna-paths).
 
 # Install Autopsy Snap
-You can download the snap package from the [releases section](https://github.com/sleuthkit/autopsy/releases) or directly from the [snap store](https://snapcraft.io/autopsy).  In order for Autopsy to run properly, snap connections will need to be properly setup, which can be done by running this script: `for connection in dm-crypt block-devices fuse-support removable-media mount-observe system-files-dev system-files-hugepages hugepages-control desktop-launch; do sudo snap connect "autopsy:$connection"; done`.  See the [snap README](./snap/README.md) for more information.
+Autopsy comes in a [Snap package](https://snapcraft.io/about).  See the [Snap README](./snap/README.md) for installation instructions and more information.
 
 # Installing Prerequisites
 - **Linux**: Run [`linux_macos_install_scripts/install_prereqs_ubuntu.sh`](./linux_macos_install_scripts/install_prereqs_ubuntu.sh).

snap/README.md

@@ -1,6 +1,10 @@
 ## Installing Snap
 
-An Autopsy [snap package](https://snapcraft.io/) file can be installed by running `sudo snap install --dangerous autopsy.snap`.  The `--dangerous` needs to be specified because the snap package isn't signed (see [install modes](https://snapcraft.io/docs/install-modes#heading--dangerous) for more information).  By default, snap doesn't allow certain interactions with the operating system.  These [Super-privileged connections](https://snapcraft.io/docs/super-privileged-interfaces) may need to be connected.  This can be done manually by running `snap connections autopsy` to determine any missing connections, and then running `snap connect autopsy:home` replacing `home` with the name of the plug.  Another option is to run this script, which will connect all missing plugs: `for connection in dm-crypt block-devices fuse-support removable-media mount-observe system-files-dev system-files-hugepages hugepages-control desktop-launch; do sudo snap connect "autopsy:$connection"; done`.  One other possible option may be to install the application with `--devmode` instead of `--dangerous`.  The `--devmode` flag is more permissive and will allow all connections to the operating system.  More information on interface management can be found at the [snapcraft website](https://snapcraft.io/docs/interface-management).
+The Snap Store has a snap package for [Autopsy](https://snapcraft.io/autopsy).  You can install Autopsy by running `sudo snap install autopsy`.  You can also install the snap from our [release section](https://github.com/sleuthkit/autopsy/releases) by downloading the `.snap` file asset and locally running  `sudo snap install --dangerous /path/to/autopsy.snap`.  The `--dangerous` needs to be specified because the snap package isn't signed (see [install modes](https://snapcraft.io/docs/install-modes#heading--dangerous) for more information).  Also, look at the [connections](#setting-snap-connections) section for important permission information.
+
+## Setting Snap Connections
+
+By default, snap doesn't allow certain interactions with the operating system.  These [Super-privileged connections](https://snapcraft.io/docs/super-privileged-interfaces) may need to be connected.  This can be done manually by running `snap connections autopsy` to determine any missing connections, and then running `snap connect autopsy:home` replacing `home` with the name of the plug.  Another option is to run this script, which will connect all missing plugs: `for connection in dm-crypt block-devices fuse-support removable-media mount-observe system-files-dev system-files-hugepages hugepages-control desktop-launch; do sudo snap connect "autopsy:$connection"; done`.  More information on interface management can be found at the [snapcraft website](https://snapcraft.io/docs/interface-management).
 
 ## Running Autopsy
 
@@ -20,8 +24,8 @@ The version of Autopsy can be updated manually by modifying fields relating to g
 
 ### Solr won't run
 
-An error like "Local Solr Server did not respond to status request" or something similar, may indicate that not all snap connections may have been connected.  By default, snap doesn't allow certain interactions with the operating system.  These [Super-privileged connections](https://snapcraft.io/docs/super-privileged-interfaces) may need to be connected.  This can be done manually by running `snap connections autopsy` to determine any missing connections, and then running `snap connect autopsy:home` replacing `home` with the name of the plug.  Another option is to run this script, which will connect all missing plugs: `for connection in dm-crypt block-devices fuse-support removable-media mount-observe system-files-dev system-files-hugepages hugepages-control desktop-launch; do sudo snap connect "autopsy:$connection"; done`.  One other possible option may be to install the application with `--devmode` instead of `--dangerous`.  The `--devmode` flag is more permissive and will allow all connections to the operating system.  More information on interface management can be found at the [snapcraft website](https://snapcraft.io/docs/interface-management).
+An error like "Local Solr Server did not respond to status request" or something similar, may indicate that not all snap connections may have been connected.  By default, snap doesn't allow certain interactions with the operating system.  You may need to manually connect these connections.  See the [connections section](#setting-snap-connections) for more information.
 
 ### There are no local disks for processing
 
-Autopsy looks at the block devices in the `/dev` directory for local disks to process.  If autopsy can't read block devices in that directory, it won't show the local disk.  In most instances, starting autopsy with a command like `sudo -g disk autopsy` should give autopsy the right permissions to view local disks.  This assumes that the `disk` group has read rights to local disks (i.e. `/dev/sda1`).  Appropriate permissions can be determined by running something like `ls -l /dev` looking for the permissions required for the local disks.  Then autopsy should be started in such a way that the `$USER` and `$HOME` are preserved (i.e. running as root may be problematic), but the user account and, consequently, autopsy, has sufficient permissions to access local disk block devices.
+Autopsy looks at the block devices in the `/dev` directory for local disks to process.  If autopsy can't read block devices in that directory, it won't show the local disk.  You may need to set the connections for the Autopsy snap that aren't set manually.  See the [connections section](#setting-snap-connections) for more information.  You may also need to run autopsy with the right OS permissions.  In most instances, starting autopsy with a command like `sudo -g disk autopsy` should give autopsy the right permissions to view local disks.  This assumes that the `disk` group has read rights to local disks (i.e. `/dev/sda1`).  Appropriate permissions can be determined by running something like `ls -l /dev` looking for the permissions required for the local disks.  Then autopsy should be started in such a way that the `$USER` and `$HOME` are preserved (i.e. running as root may be problematic), but the user account and, consequently, autopsy, has sufficient permissions to access local disk block devices.