Merge pull request #33 from LibraryCarpentry/fix/consolidate-pseudocode

Consolidate solutions into pseudocode episode

Author: jt14den

config.yaml

@@ -64,7 +64,6 @@ episodes:
 - computation_practice.md
 - computation_programming.md
 - pseudocode.md
-- solutions.Rmd
 
 
 # Information for Learners

episodes/pseudocode.md

@@ -140,6 +140,12 @@ One way to do that is to check we have coded the workflow correctly *before* we
 
 Write some pseudocode for that step of the process.
 
+::: solution
+To prevent accidental deletion of files, we could introduce a step to check whether or not to delete a file, e.g., by using the remove command `rm` in the Unix shell with an `-i` flag. The `-i` flag forces the system to ask for confirmation on whether or not to delete a file. One can answer either **Y** or **N** to the example below.
+
+![Confirming a remove command](fig/code-in-shell.png){alt="RM command in the shell", width="75%"}
+:::
+
 ::::::::::::::
 
 ::: challenge
@@ -175,10 +181,6 @@ Again, a shell script could be used to automate this work. Given that these task
 
 -------------------
 
-Some potential solutions to these practice coding exercises can be found on the [Solutions](/solutions.html) page.
-
----------------------------------
-
 #### Learning to program
 
 This lesson should help you prepare to learn to code by understanding the process that coders use to break complex problems down into programmable parts.