fix(docs): fix code formatting when multiple tabs are used

.github/workflows/docs-sync.yml

@@ -11,6 +11,7 @@ on:
 
 jobs:
   sync:
+    if: github.repository == 'rivet-dev/actors'
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4

.github/workflows/mirror-swift.yml

@@ -11,6 +11,7 @@ on:
 
 jobs:
   mirror:
+    if: github.repository == 'rivet-dev/actors'
     runs-on: ubuntu-latest
     steps:
       - name: Checkout

docs/content/docs/authentication.mdx

@@ -8,16 +8,20 @@ skill: true
 
 <Tabs>
 <Tab title="Rivet Cloud">
+
 	Actors are private by default on Rivet Cloud. Only requests with the publishable token can interact with actors.
 
 	- **Backend-only actors**: If your publishable token is only included in your backend, then authentication is not necessary.
 	- **Frontend-accessible actors**: If your publishable token is included in your frontend, then implementing authentication is recommended.
+
 </Tab>
 <Tab title="Self-Hosted">
+
 	Actors are public by default on self-hosted Rivet. Anyone can access them without a token.
 
 	- **Only accessible within private network**: If Rivet is only accessible within your private network, then authentication is not necessary.
 	- **Rivet exposed to the public internet**: If Rivet is configured to accept traffic from the public internet, then implementing authentication is recommended.
+
 </Tab>
 </Tabs>
 

docs/content/docs/connections.mdx

@@ -25,7 +25,9 @@ For example:
 There are two ways to define an actor's connection state:
 
 <Tabs>
+
 	<Tab title="connState">
+
 		Define connection state as a constant value:
 
 		<CodeSnippet file="examples/docs/actors-connections/conn-state-const.ts" />
@@ -34,6 +36,7 @@ There are two ways to define an actor's connection state:
 	</Tab>
 
 	<Tab title="createConnState">
+
 		Create connection state dynamically with a function called for each connection:
 
 		<CodeSnippet file="examples/docs/actors-connections/conn-state-dynamic.ts" />

docs/content/docs/crash-course.mdx

@@ -46,9 +46,12 @@ Persistent data that survives restarts, crashes, and deployments. State is persi
 
 <Tabs>
 <Tab title="Static Initial State">
+
 <CodeSnippet file="examples/docs/actors-crash-course/state-static.ts" />
+
 </Tab>
 <Tab title="Dynamic Initial State">
+
 <CodeSnippet file="examples/docs/actors-crash-course/state-dynamic.ts" />
 
 </Tab>
@@ -80,9 +83,12 @@ Temporary data that doesn't survive restarts. Use for non-serializable objects (
 
 <Tabs>
 <Tab title="Static Initial Vars">
+
 <CodeSnippet file="examples/docs/actors-crash-course/vars-static.ts" />
+
 </Tab>
 <Tab title="Dynamic Initial Vars">
+
 <CodeSnippet file="examples/docs/actors-crash-course/vars-dynamic.ts" />
 
 </Tab>
@@ -114,9 +120,12 @@ Access the current connection via `c.conn` or all connected clients via `c.conns
 
 <Tabs>
 <Tab title="Static Connection Initial State">
+
 <CodeSnippet file="examples/docs/actors-crash-course/conn-static.ts" />
+
 </Tab>
 <Tab title="Dynamic Connection Initial State">
+
 <CodeSnippet file="examples/docs/actors-crash-course/conn-dynamic.ts" />
 
 </Tab>
@@ -186,9 +195,12 @@ Use `UserError` to throw errors that are safely returned to clients. Pass `metad
 
 <Tabs>
 <Tab title="Actor">
+
 <CodeSnippet file="examples/docs/actors-crash-course/errors-actor.ts" />
+
 </Tab>
 <Tab title="Client">
+
 <CodeSnippet file="examples/docs/actors-crash-course/errors-client.ts" />
 
 </Tab>