New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 02-filedir.md #693

Open
wants to merge 1 commit into
base: gh-pages
from

Conversation

Projects
None yet
2 participants
@cryptic0

cryptic0 commented Jan 25, 2018

Added wording to clarify command descriptions better.

Update 02-filedir.md
Added wording to clarify command descriptions better.
@shwina

Thanks! A few small changes requested.

@@ -193,12 +193,12 @@ because its name begins with `/`.
Underneath `/Users`,
we find one directory for each user with an account on Nelle's machine,
her colleagues the Mummy and Wolfman.
her colleagues the `imhotep` and `larry`.

This comment has been minimized.

@shwina

shwina Apr 4, 2018

Member

We don't need the the, anymore. So just:

her colleagues imhotep and larry.


![Home Directories](../fig/home-directories.svg)

The Mummy's files are stored in `/Users/imhotep`,
Wolfman's in `/Users/larry`,
The user imhotep's files are stored in `/Users/imhotep`,

This comment has been minimized.

@shwina

shwina Apr 4, 2018

Member

Previously, we used monospaced text when refering to imhotep and larry; do you think we should do that consistently throughout?

@@ -442,7 +442,7 @@ To navigate through the `man` pages,
you may use the up and down arrow keys to move line-by-line,
or try the "b" and spacebar keys to skip up and down by a full page.
To search for a character or word in the `man` pages,
use "/" followed by the character or word you are searching for.
use "/" followed by the character or word you are searching for. At times, a search will result in multiple hits. If so, you can move between hits using `n` key (for moving forward) and `N` key (for moving backward).

This comment has been minimized.

@shwina

shwina Apr 4, 2018

Member
  1. The surrounding text uses double quotes when referring to a key, e.g., "b", not b. What convention to use?
  2. It may be confusing to refer to both an "n" key and also an "N" key (there is only one N key on the keyboard). Perhaps we should avoid use of the word "key" throughout. How does this sound?

At times, a search will result in multiple hits. If so, you can move between hits using n (for moving forward) and N (for moving backward)

-- not using the word key.

@@ -540,8 +540,7 @@ $ cd data
{: .bash}

These commands will move us from our home directory onto our Desktop, then into
the `data-shell` directory, then into the `data` directory. `cd` doesn't print anything,
but if we run `pwd` after it, we can see that we are now
the `data-shell` directory, then into the `data` directory. You will notice that `cd` doesn't print anything. This is normal. Many linux commands will not output anything to the screen when successfully executed. But if we run `pwd` after it, we can see that we are now

This comment has been minimized.

@shwina

shwina Apr 4, 2018

Member

Let's avoid "linux commands" in favour of "shell commands".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment