Sync open source content 🐝 (from 7952eb7db1acf0b4d89b8a3d6da43938c1d15ce8)

Author: beezythebot

api-design/developer-experience.mdx

@@ -35,11 +35,12 @@ import stripe
 stripe.api_key = "sk_test_4eC39HqLyjWDarjtT1zdp7dc"
 
 intent = stripe.PaymentIntent.create(
-    amount=1000,
-    currency="usd",
-    payment_method_types=["card"],
+amount=1000,
+currency="usd",
+payment_method_types=["card"],
 )
-```
+
+````
 
   </div>
   <div className="md:w-1/2">
@@ -57,7 +58,8 @@ data = {
 }
 response = requests.post(url, headers=headers, data=data)
 print(response.json())
-```
+````
+
   </div>
 </div>
 
@@ -103,7 +105,7 @@ Understanding the audience is the first step to creating an API that meets their
 The difference between a good and bad API often comes down to onboarding. Just ask [@levelsio](https://x.com/levelsio/status/1853774638473437451), who compared xAI and Google Gemini's APIs:
 
 <div className="mx-auto max-w-md">
-![levelsio tweet](./assets/twitter-levels-screenshot.png)
+  ![levelsio tweet](./assets/twitter-levels-screenshot.png)
 </div>
 
 While xAI needed only an API key, Google Gemini required multiple sign-ups, portal logins, and complex installation steps. For enterprise teams, inconsistent authentication across endpoints or juggling multiple keys can be equally frustrating.
@@ -148,7 +150,7 @@ Think of the dashboard as more than just a control panel, it's a trust-building
 
 The foundation of great developer experience is a well-designed, intuitive API. No amount of documentation or tooling can compensate for an overcomplicated API design.
 
-REST is *almost* always the right choice for an API. While alternatives like [GraphQL](https://graphql.org/) offer powerful features, they also introduce complexity that most applications don't need. Unless there are specific use-cases that demand more flexibility, stick with REST - it's well-understood, widely supported, and gets the job done.
+REST is _almost_ always the right choice for an API. While alternatives like [GraphQL](https://graphql.org/) offer powerful features, they also introduce complexity that most applications don't need. Unless there are specific use-cases that demand more flexibility, stick with REST - it's well-understood, widely supported, and gets the job done.
 
 Remember, most people don't need the engineering patterns used by tech giants. Start simple, and only add complexity when real usage demands it. The goal is to make life easier for developers, not to just to have fun playing around with the latest architectural patterns.
 

docs/customize/code/code-regions/java.mdx

@@ -22,7 +22,6 @@ java:
 The Speakeasy examples repository has a [full example](https://github.com/speakeasy-api/examples/tree/main/customcode-sdkclasses-java) of a Java SDK
 that uses custom code regions.
 
-
 ## Regions
 
 Below are the available code regions in Java SDKs.
@@ -31,12 +30,12 @@ Below are the available code regions in Java SDKs.
 
 Java SDK classes can have two code regions:
 
-* `// #region imports` - allows the addition of imports to an SDK file needed for
-custom methods and properties. This region must be located at the top of the
-file alongside generated imports.
-* `// #region sdk-class-body` - allows the addition of custom methods and
-properties to an SDK class. This region must be located in the body of a Java
-SDK class alongside generated methods and properties.
+- `// #region imports` - allows the addition of imports to an SDK file needed for
+  custom methods and properties. This region must be located at the top of the
+  file alongside generated imports.
+- `// #region sdk-class-body` - allows the addition of custom methods and
+  properties to an SDK class. This region must be located in the body of a Java
+  SDK class alongside generated methods and properties.
 
 ## Managing dependencies
 
@@ -102,4 +101,4 @@ public class Todos implements
         ...
     }
 }
-```
+```

docs/customize/code/code-regions/overview.mdx

@@ -3,12 +3,10 @@ title: Custom code regions
 description: "Learn how to use custom code regions to generate code in a specific location."
 ---
 
-import { Callout } from "@/mdx/components";  
+import { Callout } from "@/mdx/components";
 
 # Custom code regions
 
-
-
 <Callout title="Availability" type="info">
   Custom code regions are only available for [Enterprise users](/pricing).
   Custom code regions must be enabled in `settings/billing` under the account.