Merge pull request #5 from jbusche/jbusche-feedback1

Some small usability suggestions

Author: jjasghar

docs/lab-1/README.md

@@ -23,7 +23,7 @@ Many open LLMs available today license the model itself for derivative work, but
 
 Granite Code comes in a wide range of sizes to fit your workstation's available resources. Generally, the bigger the model, the better the results, with a tradeoff: model responses will be slower, and it will take up more resources on your machine. We chose the 20b option as my starting point for chat and the 8b option for code generation. Ollama offers a convenient pull feature to download models:
 
-Open up your terminal, and run the following commands:
+Open up a second terminal, and run the following commands:
 
 ```bash
 ollama pull granite-code:20b

docs/lab-2/README.md

@@ -16,7 +16,8 @@ Before we go any farther, write in "Who is batman?" to verify that `ollama`,
 VSCode, and `continue` are all working correctly.
 
 !!! troubleshooting
-    If Continue is taking a long time to respond, restart Visual Studio Code. If that doesn't resolve your issue, restart `ollama`.
+    If Continue is taking a long time to respond, make sure your terminal with `ollama serve` is still running.  If Ollama is running, restart Visual Studio Code. 
+    If that doesn't resolve your issue, restart Ollama.
 
 If you would like to go deeper with `continue`, take a look at the [official Continue.dev how-to guide](https://docs.continue.dev/how-to-use-continue).
 Its worth taken the moment if you want, otherwise, when you get home and try this on your own
@@ -32,6 +33,9 @@ this technology is there to support you, not _do_ your work.
 Now, lets open up VSCode and have it look something like the following:
 ![batman](../images/whoisbatman.png)
 
+!!! troubleshooting
+    If you lose the Continue pane in VSCode, you can re-enable it in VSCode by clicking at the top of the screen under "View --> Appearance --> Secondary Side Bar" and then the Continue window will be visiable again.
+
 ## Building out `main.py`
 
 Now create a new file, and put it in a new directory. Normally it's `ctrl-n` or `command-n` call it
@@ -74,7 +78,7 @@ and raise your hand the TAs will want to see it), but at least in this example w
 
 ## First pass at debugging
 
-I'll run the following commands to build up an virtual environment, and install some modules, lets
+We'll run the following commands to build up an virtual environment, and install some modules, lets
 see how far we get.
 
 !!! tip
@@ -120,7 +124,7 @@ For me, all I had to do was remove those extra spaces, but I'd be curious to kno
 
 ## Second pass at debugging
 
-Now that I've clean it up, and it seems I had to do some importing:
+Now that I've cleaned it up, and it seems I had to do some importing:
 
 ```python
 import tkinter

docs/pre-work/README.md

@@ -34,6 +34,10 @@ After the installation is complete, install [ollama](https://ollama.com) via `br
 brew install ollama
 ```
 
+### Windows installation steps
+
+Install ollama via the website [here](https://ollama.com/download/windows).
+
 ## Visual Studio Code
 
 #### Mac installation steps