Skip to content

Commit 9ce5ef2

Browse files
authored
Added curly brackets to some variables
1 parent 974f16a commit 9ce5ef2

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

lessons/07_permissions_and_environment_variables.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -222,7 +222,7 @@ In this lesson, we are going to focus on two most commonly encountered environme
222222
* `${HOME}` defines the full path for the home directory of a given user.
223223
* `${PATH}` defines a list of directories to search in when looking for a command/program to execute.
224224

225-
Environment variables, in most systems, are called or denoted with a "$" before the variable name, just like a regular variable. Like regular variables, we can also wrap them in `{}` in order to be more explicit about the variable name. Let's use the `echo` command to see what is stored in `$HOME`:
225+
Environment variables, in most systems, are called or denoted with a "$" before the variable name, just like a regular variable. Like regular variables, we can also wrap them in `{}` in order to be more explicit about the variable name. Let's use the `echo` command to see what is stored in `${HOME}`:
226226

227227
```bash
228228
$ echo ${HOME}
@@ -231,7 +231,7 @@ $ echo ${HOME}
231231
You should see the path to your home directory. `${HOME}` can be used instead of the `~` (if you want to type 4 more characters).
232232

233233

234-
`$HOME` is pretty straightforward, how about we take a look at what is stored in the `$PATH` variable:
234+
`${HOME}` is pretty straightforward, how about we take a look at what is stored in the `${PATH}` variable:
235235

236236
```bash
237237
$ echo ${PATH}

0 commit comments

Comments
 (0)