Remove redundant index-vanilla.html backup file

index.html is already the vanilla JS version

Author: notionparallax

index-vanilla.html

@@ -8,7 +8,7 @@ we revisit a lot of the ideas mentioned in the lecture in the text below too, so
 
 <iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/NMbHLzQPYE8" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 
-## Questions!
+## Questions
 
 These questions are all anonymous. They're separate forms so that we can't tie the responses together. We'll talk about this kind of thing in one of the later lectures in this course.
 
@@ -101,13 +101,13 @@ Your email address, for better or worse, is your central identity. **Don't** use
 If you're not sure if you've got a good email address, (or GitHub user name) ask me what I think.
 <!-- TODO put new tutor name in here -->
 
-#### Get a GitHub account!
+#### Get a GitHub account
 
 1. Go to [github.com](https://github.com/) and **Sign Up**. The same advice about not making your email address embarrassing applies to your github username. Imagine that you're 40, you're the CEO of a major company and having to tell someone that your github user name is <code>eat_a_bag_of_clicks</code> or, even worse <code>z123456</code>. 🤮☹️😾😡😖
 2. Fill in your real name
 3. Upload a photo of your face as your profile picture. We need this so that we can work out who you are.
 
-#### Get a StackOverflow account!
+#### Get a StackOverflow account
 
 1. Go to [stackoverflow.com](https://stackoverflow.com/) and **Sign Up**.
 
@@ -265,7 +265,7 @@ TIP: You can type a <code>../c</code> and then press [tab] and the terminal will
 
 In this course the tests are already written for you. They check if your code does what it's supposed to do. To run the tests, you write, at the terminal:
 
-> `cd ../course && pytest set1/`
+> `pytest ../course/set1/`
 
 Then press enter.
 
@@ -321,8 +321,8 @@ We're going to talk about git and commits a lot more in the coming weeks, but fo
 1. First thing you need to do is tell git who you are. Type\* these two commands into your terminal.
 
    ```
-   $ git config --global user.email "email@example.com"
-   $ git config --global user.name "Ben Doherty"
+   git config --global user.email "email@example.com"
+   git config --global user.name "Ben Doherty"
    ```
 
    Three things:

md/week1.md

@@ -10,11 +10,10 @@
 
 Also, I've started a list of [useful commands and important words](useful_commands.md). If you want to add to it, you can make a pull request, or ask me to add to the list.
 
-# Issues:
+# Issues
 
 If you didn't get a suite of beautiful green ticks last week, then you need to talk to a tutor as soon as you can. That isn't many of you, so we're looking good for this week!
 
-
 ### Updating the tests
 
 As we go through, there are new cases that we need to test for. For example, at the moment you can pass the lab book test by deleting everything in the `readme.md` file and saving it. It's not checking for empty files, only that you've changed the file. _However_ that won't always be the case, we'll update the tests when we find new reasons to. So what does this mean to you? Well, there's only one set of tests, the repo that holds your tests is the same one that holds my set. So if you want to make sure you're using the same tests as I am, you need to pull them down sometimes.
@@ -57,7 +56,7 @@ Each set has a lab book file already made for you. All you need to do is fill it
 
 Then you can write in the things you've tried and what happened. The instructions on how you use the debugger, or how to open a folder, or the nuances of a particular algorithm. Or how you feel today!
 
-# Lecture—Let's learn some python!
+# Lecture—Let's learn some python
 
 You should probably watch these in the order I've posted them, but I'm not your dad, you do whatever you want.
 
@@ -278,7 +277,7 @@ In exercise 3, the `fix_it` function asks about an engineeringFlowchart. This is
 
 1. Optional: Read _[The Oregon Trail Game: Crossing Rivers](http://www.died-of-dysentery.com/stories/crossing-rivers.html)_ and see if you can write the flow control (`if`, `elif` and `else`) statements that would give you the results in this image: ![](http://www.died-of-dysentery.com/images/chap13-doc-ford-algorithm.png). It's not going to be tested, it's more about stretching your thinking process.
 
-## Optional Reading:
+## Optional Reading
 
 These aren't a part of your marks, but they'll give you a sense of the culture of this kind of work.