diff --git a/docs/01-getting-started/02-setup.md b/docs/01-getting-started/02-setup.md
index 73641e1ac..758a82b5e 100644
--- a/docs/01-getting-started/02-setup.md
+++ b/docs/01-getting-started/02-setup.md
@@ -17,16 +17,14 @@ Preferably, you should run the setup from inside an existing repository. NUKE wi
 
 During the setup, you'll be asked several questions to configure your build to your preferences:
 
-<p style={{maxWidth:'700px'}}>
-    <AsciinemaPlayer
-        src="/casts/setup.cast"
-        idleTimeLimit={2}
-        // autoplay={true}
-        poster="npt:5.715135"
-        preload={true}
-        // terminalFontFamily="'JetBrains Mono', Consolas, Menlo, 'Bitstream Vera Sans Mono', monospace"
-        loop={true}/>
-</p>
+<AsciinemaPlayer
+    src="/casts/setup.cast"
+    idleTimeLimit={2}
+    // autoplay={true}
+    poster="npt:5.715135"
+    preload={true}
+    // terminalFontFamily="'JetBrains Mono', Consolas, Menlo, 'Bitstream Vera Sans Mono', monospace"
+    loop={true}/>
 
 **Congratulations!** 🥳 Your first build has now been set up, and you can [run the build](03-execution.md) with the default implementation!
 
diff --git a/docs/06-global-tool/00-shell-completion.md b/docs/06-global-tool/00-shell-completion.md
index 0194549b0..db902dd21 100644
--- a/docs/06-global-tool/00-shell-completion.md
+++ b/docs/06-global-tool/00-shell-completion.md
@@ -67,13 +67,12 @@ complete -fc nuke --arguments '(nuke :complete (commandline -cp))'
 
 You can complete targets, parameters, and enumeration values by hitting the <kbd>TAB</kbd> key:
 
-<p style={{maxWidth: '750px'}}>
-    <AsciinemaPlayer
-        src="/casts/shell-completion.cast"
-        idleTimeLimit={1}
-        autoplay={true}
-        poster="npt:12.077312"
-        preload={true}
-        // terminalFontFamily="'JetBrains Mono', Consolas, Menlo, 'Bitstream Vera Sans Mono', monospace"
-        loop={true}/>
-</p>
+<AsciinemaPlayer
+    src="/casts/shell-completion.cast"
+    maxWidth="750px"
+    idleTimeLimit={1}
+    autoplay={true}
+    poster="npt:12.077312"
+    preload={true}
+    // terminalFontFamily="'JetBrains Mono', Consolas, Menlo, 'Bitstream Vera Sans Mono', monospace"
+    loop={true}/>
diff --git a/docs/06-global-tool/02-secrets.md b/docs/06-global-tool/02-secrets.md
index bad4a7cfe..54e4b6d4c 100644
--- a/docs/06-global-tool/02-secrets.md
+++ b/docs/06-global-tool/02-secrets.md
@@ -37,16 +37,14 @@ On macOS you can also choose to generate a password and save it to your [keychai
 
 Afterwards, you can choose from a list of secret parameters, to either set or update their values, and finally accept or discard your changes:
 
-<p style={{maxWidth:'700px'}}>
-    <AsciinemaPlayer
-        src="/casts/secrets.cast"
-        idleTimeLimit={2}
-        // autoplay={true}
-        poster="npt:4.947343"
-        preload={true}
-        // terminalFontFamily="'JetBrains Mono', Consolas, Menlo, 'Bitstream Vera Sans Mono', monospace"
-        loop={true}/>
-</p>
+<AsciinemaPlayer
+    src="/casts/secrets.cast"
+    idleTimeLimit={2}
+    // autoplay={true}
+    poster="npt:4.947343"
+    preload={true}
+    // terminalFontFamily="'JetBrains Mono', Consolas, Menlo, 'Bitstream Vera Sans Mono', monospace"
+    loop={true}/>
 
 When secrets are saved to a parameters file, they are prefixed with `v1:` to indicate the underlying encryption method: