updates for recent VS Code

006-latency/Latency.ipynb

@@ -39,11 +39,21 @@
    "source": [
     "## Starting VSCode\n",
     "\n",
-    "At a command line, create a new folder somewhere under your home directory, and clone the Python course into it:\n",
+    "**Either**, go to https://github.com/flaxandteal/python-course and, under the *Code* menu, download ZIP. Extract it somewhere handy. Then open VSCode from your Windows/Linux/Mac desktop and, from the *File* menu, select *Open Folder*. Navigate to where you extracted the ZIP, and select the **006-latency** subfolder."
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {
+    "slideshow": {
+     "slide_type": "slide"
+    }
+   },
+   "source": [
+    "**Or** at a command line, create a new folder somewhere under your home directory, and clone the Python course into it:\n",
     "\n",
     "    git clone https://github.com/flaxandteal/python-course\n",
     "    cd python-course\n",
-    "    git checkout professional\n",
     "   \n",
     "Head to the 006-latency folder:\n",
     "\n",
@@ -56,6 +66,13 @@
     "Open the `006-latency` directory from the file menu."
    ]
   },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "![Screenshot from VS Code](vscode-screenshot.png)"
+   ]
+  },
   {
    "cell_type": "markdown",
    "metadata": {
@@ -191,7 +208,7 @@
     }
    },
    "source": [
-    "Since some of you may have a CS background and I do not, I am going to to take a risk and theme this session on measuring latency between a server and client. Please ignore the simplistic methodology - if you find a few minutes spare, feel free to improve the approach! However, the aim here is to look at the code and algorithms.\n",
+    "This session is themed on measuring latency between a server and client. Please bear in mind that this uses a fairly rough approach to accuracy - if you find a few minutes spare, feel free to improve the approach! However, the aim here is to look at the code and algorithms.\n",
     "\n",
     "More broadly, for those who are coming from an engineering end, I can say from experience that if you start to scale up your number of simulations, you will be looking for bottlenecks and profiling. There are better, tailored utilities for doing so, but this should give you an idea about how to think about the problem."
    ]
@@ -212,7 +229,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "On the right hand side, you will see an icon of a ladybird-like bug. Click it, and notice that the left-hand side changes to a set of panels:\n",
+    "On the right hand side, you will see an icon of a play button / ladybird-like bug. Click it, and notice that the left-hand side changes to a set of panels:\n",
     "\n",
     "* Variables\n",
     "* Watch\n",
@@ -691,7 +708,7 @@
     }
    },
    "source": [
-    "Hit F5, or go to `Run->Run`\n",
+    "Hit F5, or go to `Run->Run Without Debugging`\n",
     "\n",
     "If you get a dialog saying \"`Run Settings`\", choose \"`Execute in a new dedicated Python console`\" and continue."
    ]
@@ -788,7 +805,7 @@
     }
    },
    "source": [
-    "First we introduce the concept of a *generator*. This is a Python construct that embeds a loop in quite a few possible places. Mostly you will see them used to create lists and dicts. The format is (for basic use):"
+    "First we introduce the concept of a *list comprehension*. This is a Python construct that embeds a loop in quite a few possible places. Mostly you will see them used to create lists and dicts. The format is (for basic use):"
    ]
   },
   {