update noSerdeLayer

Author: devalog

fern/products/sdks/pages/typescript/configuration.mdx

@@ -18,7 +18,7 @@ groups:
 
 ## SDK configuration options
 
-<ParamField path="outputSourceFiles" type="boolean" default="false">
+<ParamField path="outputSourceFiles" type="boolean" default="true">
   When enabled, the generator outputs raw TypeScript files. When disabled (the default), outputs `.js` and `d.ts` files. 
 
   <Note>This only applies when dumping code locally. This configuration is ignored when publishing to Github or npm.</Note>
@@ -344,20 +344,19 @@ By default, names are based on the organization and API names in the Fern Defini
 
 </ParamField>
 
-<ParamField path="noSerdeLayer" type="boolean" default="false">
- By default, the generated client includes a layer for serializing requests and deserializing responses. This has three benefits:
+<ParamField path="noSerdeLayer" type="boolean" default="true">
+
+No serialization/deserialization code is generated by default. The client uses `JSON.parse()` and `JSON.stringify()` instead of the default Serde layer. 
+
+ When `noSerdeLayer: false`, the generated client includes a layer for serializing requests and deserializing responses. This has three benefits:
 
 	1. The client validates requests and response at runtime (client-side).
 
 	1. The client can support complex types like `Date` and `Set`.
 
 	1. The generated types can stray from the wire/JSON representation to be more
-	   idiomatic. For example, when `noSerdeLayer` is disabled, all properties are `camelCase`,
-	   even if the server is expecting `snake_case`.
-
-  When `noSerdeLayer` is enabled, no serialization/deserialization code is generated. The client uses `JSON.parse()` and `JSON.stringify()` instead of the default Serde layer. 
+	   idiomatic. For example, when the Serde layer is enabled (`noSerdeLayer: false`), all properties are `camelCase`, even if the server is expecting `snake_case`.
 
- 
 </ParamField>
 
 <ParamField path="retainOriginalCasing" type="boolean" default="false">