Replace deprecated commands

docs/tutorials/soar_tutorial/05.md

@@ -242,12 +242,12 @@ does not have an evaluation with a value. The operator will first create
 an evaluation and later compute the value.
 
 ```Soar
-Selection*propose*evaluate-operator
+selection*propose*evaluate-operator
 ```
 
-If the state is named selection and there is an item that does not have
-an evaluation with a value, then propose the evaluate-operator for that
-item.
+> If the state is named selection and there is an item that does not have
+> an evaluation with a value, then propose the evaluate-operator for that
+> item.
 
 The tricky part of translating this into a rule is the test that there
 is an item without an evaluation with a value. The item can be matched
@@ -727,10 +727,10 @@ working memory elements that were not necessary to produce the result,
 then the chunk will also test for them and the new rule will be overly
 specific.
 
-To invoke chunking, type in: `learn –-on` at the prompt of the interaction
-window or add `learn –-on` as a line in the file containing your rules.
+To invoke chunking, type in: `chunk always` at the prompt of the interaction
+window or add `chunk always` as a line in the file containing your rules.
 You will also want to see when chunks are created and fire, which is
-enabled using: `watch -–chunks –-print`. Before rerunning your program,
+enabled using: `watch --chunks`. Before rerunning your program,
 try to predict what types of rules will be learned. There should be two
 different types of rules because there are two different types of
 results: preferences created by comparing evaluations in the selection