adjust more image sizes

docs/getting-started/email-recovery.md

@@ -42,7 +42,7 @@ Authorization for email recovery is based on our usual activity authorization: o
     <img
         src="/img/diagrams/email_recovery_authorization.png"
         alt="email recovery authorization"
-        style={{ width: 500, height: 200 }}
+        style={{ width: 500 }}
     />
 </p>
 

docs/integration-guides/export-wallets.md

@@ -28,7 +28,11 @@ In the rest of this guide we'll assume you are using these helpers.
 Here's a diagram summarizing the wallet export flow step-by-step ([direct link](/img/wallet_export_steps.png)):
 
 <p style={{ textAlign: "center" }}>
-    <img src="/img/wallet_export_steps.png" alt="wallet export steps" style={{ height: 200 }} />
+    <img
+        src="/img/wallet_export_steps.png"
+        alt="wallet export steps"
+        style={{ width: 600 }}
+    />
 </p>
 
 Let's review these steps in detail:
@@ -75,7 +79,11 @@ Let's review these steps in detail:
 Export is complete! The iframe now displays a numbered 3-column grid of words that form the mnemonic, directly to your end user.
 
 <p style={{ textAlign: "center" }}>
-    <img src="/img/wallet_export_mnemonic.png" alt="wallet mnemonic" style={{ height: 280 }} />
+    <img
+        src="/img/wallet_export_mnemonic.png"
+        alt="wallet mnemonic"
+        style={{ width: 330 }}
+    />
 </p>
 
 The exported wallet will remain stored within Turnkey’s infrastructure. In your Turnkey dashboard, the exported user Wallet will be flagged as “Exported”.  
@@ -113,7 +121,11 @@ It works by anchoring export in a **target encryption key** (TEK). This target e
  The following diagram summarizes the flow:
 
 <p style={{ textAlign: "center" }}>
-    <img src="/img/wallet_export_cryptography.png" alt="export cryptography" style={{ height: 320 }} />
+    <img
+        src="/img/wallet_export_cryptography.png"
+        alt="export cryptography"
+        style={{ height: 460 }}
+    />
 </p>
 
 The public part of this key pair is passed as a parameter inside of a signed `EXPORT_WALLET` or `EXPORT_PRIVATE_KEY` activity.

docs/passkeys/options.md

@@ -26,8 +26,6 @@ Number of seconds before "giving up". The browser will simply show a timeout pop
     alt="authenticatorAttachment unspecified"
     style={{ width: 360 }} />
 </p>
-<br/>
-<br/>
 
 This UI isn't very helpful, so we recommend making the timeout long (5 minutes). The less your users see this, the better.
 
@@ -65,7 +63,7 @@ Turnkey currently supports P256 only. In the near future Turnkey will support RS
 
 The `user` field has three sub-fields:
 - `id`: also known as "user handle", isn't visible to the end-user. We **strongly recommend setting this to a random value** (e.g. `const id = new Uint8Array(32); crypto.getRandomValues(id)`) to make sure a new passkey is created. Be aware: **if you accidentally set this value to an existing user handle, the corresponding passkey will be overridden!**. [This section of spec](https://www.w3.org/TR/webauthn-2/#dictionary-user-credential-params) is clear on the matter: "the user handle ought not be a constant value across different accounts, even for non-discoverable credentials".
-- `name`: this will show up in the passkey list modal (see screenshot below). We recommend setting this to something the user will recognize: their email, the name of your app, or potentially leave this up to the user:<br/>
+- `name`: this will show up in the passkey list modal (see screenshot below). We recommend setting this to something the user will recognize: their email, the name of your app, or potentially leave this up to the user:
   <p style={{ textAlign: "center" }}>
     <img src="/img/passkeys/user_name_and_display.png" alt="RPID in registration prompt" style={{ width: 360 }} />
   </p>