final drafting

Author: thescientist13

src/pages/blog/release/v0-32-0.md

@@ -1,6 +1,6 @@
 ---
 title: Release - v0.32.0
-abstract: Introducing our new AWS adapter plugin and adopting built-in TypeScript support.
+abstract: Introducing our new AWS adapter plugin and making TypeScript support built-in to Greenwood.
 published: 2025-4-12
 coverImage: /assets/blog/acorn.webp
 layout: blog
@@ -14,9 +14,9 @@ layout: blog
 
 ## What's New
 
-Along with a round of bug fixes and miscellaneous enhancements, this new Greenwood release brings with it two big new features we are excited to share. We now have an official AWS Adapter for deploying dynamic pages and routes to Lambda functions, as well as now making our TypeScript plugin officially built-in; no more plugin needed anymore! There was also a small minimum version bump for NodeJS.
+Along with a round of enhancements and bug fixes, this new Greenwood release brings with it two big new features we are excited to share. We now have an official AWS Adapter for deploying dynamic SSR pages and API routes to Lambda functions, as well as now making our TypeScript plugin officially built-in; no more plugin needed anymore to use TypeScript with Greenwood! There was also a small minimum version bump for NodeJS.
 
-This release was also the by-product of some great feedback, support, and contributions from our community. In particular the built-in TypeScript support was very much a collaborative communication process that really helped to strengthen Greenwood as a project that can be a pragmatic and productive experience to develop with. We very much enjoyed the conversations we had around this topic and the end result we produced. Thank you so much to everyone who got involved with us for this release, it means a lot to use and it's great to see what you're building with Greenwood! 💚
+This release was also the by-product of some great feedback, support, and contributions from our community. In particular the built-in TypeScript support was very much a collaborative process that really helped to strengthen Greenwood as a project that can be open to feedback and help it continue to grow as a productive experience to develop with. We very much enjoyed the conversations we had around this topic and the end result we produced. Thank you so much to everyone who got involved with us for this release, it means a lot to us and it's great to see what you're all building with Greenwood! 💚
 
 > Please refer to the [release notes](https://github.com/ProjectEvergreen/greenwood/releases/tag/v0.32.0) for the complete changelog and overview of breaking changes.
 
@@ -32,7 +32,7 @@ export default {
 };
 ```
 
-Taking into consideration that there are many methods and options for deploying to AWS, this adapter plugin is primarily focused on generating consistent and predictable build output that can be complimented by some form of [**IaC (Infrastructure as Code)**](https://en.wikipedia.org/wiki/Infrastructure_as_code) or deployment tooling of your choice. The build output will look similar to Greenwood's own [standard build output](/docs/reference/appendix/#build-output) and will be available in the _.aws-output/_ folder at the root of your project.
+Taking into consideration that there are many methods and options for deploying to AWS, this adapter plugin is primarily focused on generating consistent and predictable build output that can be complimented by some form of [**IaC (Infrastructure as Code)**](https://en.wikipedia.org/wiki/Infrastructure_as_code) or deployment tooling of your choice. The build output will look similar to Greenwood's own [standard build output](/docs/reference/appendix/#build-output) and will be available in the _.aws-output/_ folder at the root of your project after running the build command.
 
 ```shell
 .aws-output/
@@ -53,10 +53,10 @@ Taking into consideration that there are many methods and options for deploying
       products.route.js
 ```
 
-For each of the folders in the _api/_ or _routes/_ directories, it would just be a matter of creating a zip file for each folder / route, or ideally pointing your IaC tooling to those output folders. For example, here is a simplified example from our [**SST**](https://sst.dev/) example repo:
+For each of the folders in the _api/_ or _routes/_ directories, it would just be a matter of creating a zip file for each folder / route and uploading those, or ideally pointing your IaC tooling to those output folders. For example, here is a simplified example from our [**SST**](https://sst.dev/) example:
 
 ```ts
-// 1) Configure SSR pages and API routes in API Gateway
+// 1) Configure an API Gateway for routing SSR pages and API routes
 const api = new sst.aws.ApiGatewayV2("MyApi");
 
 // products page
@@ -79,7 +79,7 @@ const frontend = new sst.aws.StaticSite("MyStaticSite", {
   },
 })
 
-// 3) Configure CloudFront router with SSR pages, API routes, and static content
+// 3) Configure a CloudFront distribution with behaviors for SSR pages, API routes, and static content
 const router = new sst.aws.Router("MyRouter", {
   routes: {
     "/api/*": api.url,
@@ -95,7 +95,7 @@ const router = new sst.aws.Router("MyRouter", {
   invalidation: true,
 });
 
-// 4) Configure SST app
+// 4) Configure the SST app
 export default $config({
   app(input) {
     return {
@@ -115,7 +115,7 @@ export default $config({
 
 ## Built-in TypeScript Support
 
-With this release, Greenwood now provides built-in support for TypeScript, with the ability to fallback to using `tsc` if certain TypeScript features you're using (like Decorators, [enums, namespaces, etc](https://devblogs.microsoft.com/typescript/announcing-typescript-5-8/#the---erasablesyntaxonly-option)) are not supported through just type stripping alone. This was motivated due to [NodeJS version `>= 22.6.0`](https://nodejs.org/en/learn/typescript/run-natively) now making type stripping available by using the `--experimental-strip-types` flag. This also means you can remove Greenwood's [TypeScript plugin](https://greenwoodjs.dev/docs/plugins/typescript/) as it is has been deprecated with this release.
+With this release, Greenwood now provides built-in support for TypeScript, with the ability to fallback to using `tsc` if certain TypeScript features you're using (like Decorators, [enums, namespaces, etc](https://devblogs.microsoft.com/typescript/announcing-typescript-5-8/#the---erasablesyntaxonly-option)) are not supported through just type stripping alone. This was motivated due to [NodeJS version `>= 22.6.0`](https://nodejs.org/en/learn/typescript/run-natively) now making type stripping available through the `--experimental-strip-types` flag. This also means you can remove Greenwood's [TypeScript plugin](https://greenwoodjs.dev/docs/plugins/typescript/) as it is has been deprecated with this release.
 
 ```json
 {