From 949c1516fabd558b5b0b41d840b5de0868986aea Mon Sep 17 00:00:00 2001 From: Pat Carr Date: Feb 21 2019 19:31:31 +0000 Subject: Fix a few grammatical errors --- diff --git a/modules/ROOT/pages/silverblue-guide.adoc b/modules/ROOT/pages/silverblue-guide.adoc index c5b96b1..2ea9779 100644 --- a/modules/ROOT/pages/silverblue-guide.adoc +++ b/modules/ROOT/pages/silverblue-guide.adoc @@ -34,7 +34,7 @@ and any other form of coding listed in the document will take the form of `for c without the leading `~]$`. == Introduction -Daily use of Fedora Silverblue as an acceptable workstation is not so easy as it's +Daily use of Fedora Silverblue as an acceptable workstation is not so easy as its wonderfully seamless installation process would belie. Independence of the OS and the Apps, with respect to updates/upgrades is a benefit to stability and security. The benefits and pitfalls can come to the forefront when pushing the use case. Which @@ -68,7 +68,7 @@ The installation instructions for Silverblue can be found https://docs.fedorapro **** In the issue noted in the Introduction, the package Proselint was layered onto the rpm-ostree to solve the lacking proselint executable. If you have a preferred terminal to use, it should be layered too. **** -Answers to such questions as, Do I want to encrypt my storage media? Am I going to use the standard RXVT terminal or do I want TMUX and Terminator, or just Terminator, and how does it need to be set up? These are only a basic selection of the many potential questions that may plague a user intending on using Fedora Silverblue as their daily workstation, and we haven't even contemplated the immutable OS much yet. Each use case draws it's own set of questions needing answers to facilitate a successful installation. Throughout, and integral to these many faceted usage environments, are the individual tasks all of us users do to set up our computing environment to suit our use case needs. These tasks are the procedure we follow, whether recorded for reference or not, each time we go through the process of setting up our workstation's. Some, as indicated https://discussion.fedoraproject.org/t/how-i-automated-my-fedora-workstation-with-modular-ansible-roles/579/4[here] in a discussion at fedoraproject.org have automated their workstation setup, in this case using Ansible Roles. Then there are a couple of examples of using github to have a repo for a convenient way of being able to setup/reset a system to a known state. At a discussion about suggested approaches to correctly setup Silverblue https://discussion.fedoraproject.org/t/what-is-the-suggested-approach-es-to-correctly-set-up-a-silverblue-workstation/432[here] examples of that were offered as potential answers. +Answers to such questions as, Do I want to encrypt my storage media? Am I going to use the standard RXVT terminal or do I want TMUX and Terminator, or just Terminator, and how does it need to be set up? These are only a basic selection of the many potential questions that may plague a user intending on using Fedora Silverblue as their daily workstation, and we haven't even contemplated the immutable OS much yet. Each use case draws its own set of questions needing answers to facilitate a successful installation. Throughout, and integral to these many faceted usage environments, are the individual tasks all of us users do to set up our computing environment to suit our use case needs. These tasks are the procedure we follow, whether recorded for reference or not, each time we go through the process of setting up our workstation's. Some, as indicated https://discussion.fedoraproject.org/t/how-i-automated-my-fedora-workstation-with-modular-ansible-roles/579/4[here] in a discussion at fedoraproject.org have automated their workstation setup, in this case using Ansible Roles. Then there are a couple of examples of using github to have a repo for a convenient way of being able to setup/reset a system to a known state. At a discussion about suggested approaches to correctly setup Silverblue https://discussion.fedoraproject.org/t/what-is-the-suggested-approach-es-to-correctly-set-up-a-silverblue-workstation/432[here] examples of that were offered as potential answers. === Automatic Partitioning === Manual Partitioning @@ -101,14 +101,14 @@ practice, what this means is that the flatpak deployment of an application does normally have access to the host OS directly, or any other applications running on the host. The application is running on a runtime contained inside of the faltpak itself. If this sounds a lot like a flatpak is a container, it's because it is a -container essentially. An application in flatpak form is running inside of it's own environment +container essentially. An application in flatpak form is running inside of its own environment designed specifically to make it work as intended, irrespective of the host OS, and is quite effectively sandboxed. One of Flatpak’s main goals is to increase the security of desktop systems by isolating applications from one another. This is achieved using sandboxing and means that, by default, applications that are run with Flatpak have extremely limited access to the host environment. For day to day usage in roles that encompass the bulk of things users generally are doing at their -PC Silverblue, with it's immutable OS and flatpak'd applications proves to function +PC Silverblue, with its immutable OS and flatpak'd applications proves to function quite well. The updates are rolling along regularly just like the Fedora Workstation I had become used to, and the majority of my applications that are flatpak's work as they are intended to. @@ -123,11 +123,11 @@ the system yet. This is due entirely to the Fedora licensing scheme, since Flath allows software with non-open source license schemes to be distributed, like for instance rpmfusion-nonfree repo does in the normal Workstation version of Fedora. The user has to configure the rpmfusion-nonfree repo in order to install anything -from it's repository. In Silverblue, when installing flatpak'd applications, you +from its repository. In Silverblue, when installing flatpak'd applications, you have to configure the repository for use first. You do this with the `flatpak -remote-add` command. This command takes as it's first argument, the name you want +remote-add` command. This command takes as its first argument, the name you want to give the remote, and the URL it is located at for the second argument. In the -case of the flathub repository, I simply named mine `flathub` and it's URL is +case of the flathub repository, I simply named mine `flathub` and its URL is https://dl.flathub.org/repo/. The command becomes `flatpak remote-add flathub "https://dl.flathub.org/repo/"` without the quotes. It is also acceptable, and easier to browse to Flathub.org and select the quick setup option for Fedora, which @@ -153,7 +153,7 @@ then install the FireFox nightly build with the command `flatpak install firefox-nightly org.mozilla.FirefoxNightly` and flatpak will install the Firefox nightly build for you. You may have already come to the conclusion that you could also install it from Gnome Software since you have configured the remote, -and you would be correct but take note of the source listed on it's install icon, +and you would be correct but take note of the source listed on its install icon, it is the remote you just configured. As no doubt. some of the clever monkeys out there have likely noted when they did a remote-ls command on their configured flathub remote, there are more things listed than the app's. There are runtimes,