diff --git a/instructions/challenge_2.md b/instructions/challenge_2.md index 7379a4d..5cd5253 100644 --- a/instructions/challenge_2.md +++ b/instructions/challenge_2.md @@ -18,6 +18,6 @@ following: - Once there, the app there needs to be named `run-app`, not `app` - To ensure both locations always have the same version (e.g. during hotfixes), - make a reference from the binary location to the target location without - copying the actual file. This way, any update or change will reflect in both + make a reference from the binary location to the target location *without + copying the actual file*. This way, any update or change will reflect in both places at once without needing to manually sync them. diff --git a/instructions/challenge_3.md b/instructions/challenge_3.md index 31a1739..df7d085 100644 --- a/instructions/challenge_3.md +++ b/instructions/challenge_3.md @@ -15,5 +15,5 @@ Create that service, and get it running. You need to make sure it runs *even if the system reboots* -- meaning that if the server is restarted for any reason, the app service needs to start again *without you starting it manually*. -If for any reason you need to check out more detailed logs of the service, you -can also use the separate `journalctl` command to inspect them. +If for any reason you need to check out more detailed logs of the service you're +creating, you can also use the separate `journalctl` command to inspect them. diff --git a/instructions/challenge_4.md b/instructions/challenge_4.md index d732017..6f9634d 100644 --- a/instructions/challenge_4.md +++ b/instructions/challenge_4.md @@ -24,5 +24,5 @@ look at the `/opt/app` directory again, you may have noticed that there is a correctly-installed app binary. Once you do that, be sure to check the `systemd` and/or `journald` logs of the -new `app-deb.service` to make sure it's running successfully! (and, just like -the last one, that it would keep running after a reboot) +new `app-deb.service` to make sure it's running successfully (and, just like +the last one, that it would keep running after a reboot). diff --git a/instructions/challenge_6.md b/instructions/challenge_6.md index 9e09159..25ecd5b 100644 --- a/instructions/challenge_6.md +++ b/instructions/challenge_6.md @@ -8,7 +8,7 @@ dissappeared while on a golfing trip a few weeks past. We were told that the code was about ready to deploy, just hadn't gotten the chance to merge it into the main branch. See if you can figure out how to get it up and running. -The name of the app is 'carrot-cruncher'. The last dev got the repo set up +The name of the app is "carrot-cruncher". The last dev got the repo set up somewhere on disk, but they never said where... hopefully you'll able to find it. When you do, supposedly there was a new working branch pushed to the remote repo, so you'll need to figure out how to authenticate to that repo.