fix mistakes after merging PRs

Author: SkafteNicki

.github/workflows/pre_commit.yaml

@@ -22,7 +22,7 @@ jobs:
 
     - name: Install pre-commit
       uses: pre-commit/action@v3.0.1
-#      with: 
+#      with:
 #        continue-on-error: true
 
 #    - name: List modified files

pages/before.md

@@ -2,7 +2,7 @@
 
 When working on the exercises, I in general recommend following this structure:
 
-```
+```txt
 <02476_XXX>/                      # call this whatever you like
     ├── dtu_mlops/                # the content of this repository
     │   ├── .venv/

s1_development_environment/exercise_files/1_Tensors_in_PyTorch.ipynb

@@ -64,7 +64,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "If you are using a wsl and the kernel does not corretly connect, then Jupiter may not be corretly installed on the wsl.\n",
+    "If you are using a wsl and the kernel does not correctly connect, then Jupiter may not be correctly installed on the wsl.\n",
     "Run\n",
     "\"python3 -m jupyter --version\"\n",
     "\n",

s1_development_environment/exercise_files/fc_model.py

@@ -1,6 +1,7 @@
 import torch
 from torch import nn
 
+
 class Network(nn.Module):
     """Builds a feedforward network with arbitrary hidden layers.
 

s4_debugging_and_logging/profiling.md

@@ -247,8 +247,9 @@ result nicely (like `snakeviz` for `cProfile`) we are also going to use the tens
     prof.export_chrome_trace("trace.json")
     ```
 
-    You should be able to visualize the file by going to `chrome://tracing` in any chromium-based web browser (provided you have enabled internal debugging pages at chrome://chrome-urls).
-    Can you still identify the information printed in the previous exercises from the visualizations?
+    You should be able to visualize the file by going to `chrome://tracing` in any chromium-based web browser (provided
+    you have enabled internal debugging pages at chrome://chrome-urls). Can you still identify the information printed
+    in the previous exercises from the visualizations?
 
 5. Running profiling on a single forward step can produce misleading results, as it only provides a single sample that
     may depend on what background processes are running on your computer. Therefore it is recommended to profile

s6_the_cloud/cloud_setup.md

@@ -167,9 +167,10 @@ you want them to be able to do. The figure below shows how to do this.
 </figure>
 
 What we are going to go through right now is how to increase the quotas for how many GPUs you have available for your
-project. You can read more about quota types and levels [here](https://docs.cloud.google.com/docs/quotas/overview). By
-default, for any free accounts in GCP (or accounts using teaching credits) the default quota for GPUs that
-you can use is either 0 or 1 (their policies sometimes change). We will in the exercises below try to increase it.
+project. You can read more about quota types and levels
+[in the documentation](https://docs.cloud.google.com/docs/quotas/overview). By default, for any free accounts in GCP
+(or accounts using teaching credits) the default quota for GPUs that you can use is either 0 or 1 (their policies
+sometimes change). We will in the exercises below try to increase it.
 
 ### ❔ Exercises
 

tasks.py

@@ -1,7 +1,5 @@
 import os
 import sys
-import numpy as np
-import matplotlib.pyplot as plt
 
 from invoke import task