Fix Sphinx typos

Author: tomneep

episodes/15-coding-conventions.md

@@ -608,7 +608,7 @@ or using triple quotes as a way to 'quickly' comment out an entire block of code
 is considered bad practice.
 
 In our example case, we used the
-[Sphynx/ReadTheDocs docstring style](https://sphinx-rtd-tutorial.readthedocs.io/en/latest/docstrings.html)
+[Sphinx/ReadTheDocs docstring style](https://sphinx-rtd-tutorial.readthedocs.io/en/latest/docstrings.html)
 formatting for the `param`, `raises` and `returns` - other docstring formats exist as well.
 
 :::::::::::::::::::::::::::::::::::::::::  callout

slides/section_1_setting_up_environment.md

@@ -547,7 +547,7 @@ Start from this section heading and go to the end of the page.
   - A lot of these checks for formatting can now be done automatically with your IDE or linters, so do not spend too long absorbing them. It is good to be aware why rules are being applied, but the details of implementation are less important.
   - poll/status check at the end
 - Some comments after the exercises
-  - There are many different docstring formats, and I tend to not like the Sphynx default very much. Google or Numpy style docstrings much more readable.
+  - There are many different docstring formats, and I tend to not like the Sphinx default very much. Google or Numpy style docstrings much more readable.
   - For the exercise to improve the docstrings, no mention is made of the fact that the module docstring should include a list of the functions in the module. This is another valid improvement. (Advance to next slide to see this)
 <!-- #endregion -->