deploy: ece84f2c450d986e54acc80971225fb02f4e1d05

3 files changed, 6 insertions, 6 deletions

diff --git a/develop/development/cas.html b/develop/development/cas.html

index 77ab326199..1c3f429b80 100644
--- a/develop/development/cas.html
+++ b/develop/development/cas.html
@@ -190,17 +190,17 @@ easy to run CAS implementation built on top of Django.</p>
 <li>Create a new virtualenv: <code>python3 -m venv &lt;your virtualenv&gt;</code></li>
 <li>Activate your virtualenv: <code>source /path/to/your/virtualenv/bin/activate</code></li>
 <li>Install Django and django-mama-cas:
-<pre><code>python -m pip install &quot;django&lt;3&quot; &quot;django-mama-cas==2.4.0&quot;
+<pre><code class="language-sh">python -m pip install &quot;django&lt;3&quot; &quot;django-mama-cas==2.4.0&quot;
 </code></pre>
 </li>
 <li>Create a Django project in the current directory:
-<pre><code>django-admin startproject cas_test .
+<pre><code class="language-sh">django-admin startproject cas_test .
 </code></pre>
 </li>
 <li>Follow the <a href="https://django-mama-cas.readthedocs.io/en/latest/installation.html#configuring">install directions</a> for django-mama-cas</li>
 <li>Setup the SQLite database: <code>python manage.py migrate</code></li>
 <li>Create a user:
-<pre><code>python manage.py createsuperuser
+<pre><code class="language-sh">python manage.py createsuperuser
 </code></pre>
 <ol>
 <li>Use whatever you want as the username and password.</li>
@@ -208,7 +208,7 @@ easy to run CAS implementation built on top of Django.</p>
 </ol>
 </li>
 <li>Use the built-in Django test server to serve the CAS endpoints on port 8000:
-<pre><code>python manage.py runserver
+<pre><code class="language-sh">python manage.py runserver
 </code></pre>
 </li>
 </ol>
diff --git a/develop/development/database_schema.html b/develop/development/database_schema.html

index 3f4b14529f..218b677407 100644
--- a/develop/development/database_schema.html
+++ b/develop/development/database_schema.html
@@ -263,7 +263,7 @@ has had all background updates run.</p>
 <p>To do so, use <code>scripts-dev/make_full_schema.sh</code>. This will produce new
 <code>full.sql.postgres</code> and <code>full.sql.sqlite</code> files.</p>
 <p>Ensure postgres is installed, then run:</p>
-<pre><code>./scripts-dev/make_full_schema.sh -p postgres_username -o output_dir/
+<pre><code class="language-sh">./scripts-dev/make_full_schema.sh -p postgres_username -o output_dir/
 </code></pre>
 <p>NB at the time of writing, this script predates the split into separate <code>state</code>/<code>main</code>
 databases so will require updates to handle that correctly.</p>
diff --git a/develop/development/saml.html b/develop/development/saml.html

index 8c6b2f212a..040efb558c 100644
--- a/develop/development/saml.html
+++ b/develop/development/saml.html
@@ -196,7 +196,7 @@ the XML from step 2 as the contents.</li>
   sp_config:
     allow_unknown_attributes: true  # Works around a bug with AVA Hashes: https://github.com/IdentityPython/pysaml2/issues/388
     metadata:
-      local: [&quot;samling.xml&quot;]   
+      local: [&quot;samling.xml&quot;]
 </code></pre>
 </li>
 <li>Ensure that your <code>homeserver.yaml</code> has a setting for <code>public_baseurl</code>: