From 22220c8b67ee19532a5c2d3c8297b68a84b1c15a Mon Sep 17 00:00:00 2001
From: Commandcracker <49335821+Commandcracker@users.noreply.github.com>
Date: Fri, 31 Mar 2023 15:48:40 +0200
Subject: [PATCH] Update creating-a-reproduction.md

---
 docs/guides/creating-a-reproduction.md | 27 +++++++++++++-------------
 1 file changed, 13 insertions(+), 14 deletions(-)

diff --git a/docs/guides/creating-a-reproduction.md b/docs/guides/creating-a-reproduction.md
index d7fce2951..19a342b3e 100644
--- a/docs/guides/creating-a-reproduction.md
+++ b/docs/guides/creating-a-reproduction.md
@@ -22,24 +22,23 @@ just delete and recreate the environment. It's trivial to set up:
 
 -   Activate the environment with:
 
+    === ":fontawesome-brands-windows: Windows"
 
-=== ":fontawesome-brands-windows: Windows"
+        ``` sh
+        . venv/Scripts/activate # (1)!
+        ```
 
-    ``` sh
-    . venv/Scripts/activate # (1)!
-    ```
-    
-    1.  Your terminal should now print `(venv)` before the prompt, which is
-        how you know that you are inside an environment.
-        
-=== ":material-linux: Linux"
+        1. Your terminal should now print `(venv)` before the prompt, which is
+           how you know that you are inside an environment.
 
-    ``` sh
-    . venv/bin/activate # (1)!
-    ```
+    === ":material-linux: Linux, :material-apple: macOS"
 
-    1.  Your terminal should now print `(venv)` before the prompt, which is
-        how you know that you are inside an environment.
+        ``` sh
+        . venv/bin/activate # (1)!
+        ```
+
+        1. Your terminal should now print `(venv)` before the prompt, which is
+           how you know that you are inside an environment.
 
 -   Exit the environment with: