docs: improve clarity and conciseness across various documentation files.

Author: yamcodes

CODE_OF_CONDUCT.md

@@ -1,28 +1,28 @@
 # Contributor Covenant Code of Conduct
 
-## Our Pledge
+## Pledge
 
-We as members, contributors, and leaders pledge to make participation in our
+Members, contributors, and leaders pledge to make participation in the
 community a harassment-free experience for everyone, regardless of age, body
 size, visible or invisible disability, ethnicity, sex characteristics, gender
 identity and expression, level of experience, education, socio-economic status,
 nationality, personal appearance, race, religion, or sexual identity
 and orientation.
 
-We pledge to act and interact in ways that contribute to an open, welcoming,
+The pledge is to act and interact in ways that contribute to an open, welcoming,
 diverse, inclusive, and healthy community.
 
-## Our Standards
+## Standards
 
 Examples of behavior that contributes to a positive environment for our
 community include:
 
 - Demonstrating empathy and kindness toward other people
 - Being respectful of differing opinions, viewpoints, and experiences
 - Giving and gracefully accepting constructive feedback
-- Accepting responsibility and apologizing to those affected by our mistakes,
+- Accepting responsibility and apologizing to those affected by mistakes,
   and learning from the experience
-- Focusing on what is best not just for us as individuals, but for the
+- Focusing on what is best not just for individuals, but for the
   overall community
 
 Examples of unacceptable behavior include:
@@ -38,7 +38,7 @@ Examples of unacceptable behavior include:
 
 ## Enforcement Responsibilities
 
-Community leaders are responsible for clarifying and enforcing our standards of
+Community leaders are responsible for clarifying and enforcing standards of
 acceptable behavior and will take appropriate and fair corrective action in
 response to any behavior that they deem inappropriate, threatening, offensive,
 or harmful.
@@ -52,15 +52,14 @@ decisions when appropriate.
 
 This Code of Conduct applies within all community spaces, and also applies when
 an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
+Examples of representing the community include using an official e-mail address,
 posting via an official social media account, or acting as an appointed
 representative at an online or offline event.
 
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement by contacting the maintainer team
-.
+reported to community leaders responsible for enforcement by contacting the maintainer.
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Developer's Guide
 
-Hey there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great and we truly appreciate your time and effort.
+Hey there! Contributing to this project is highly encouraged. Community help is essential for maintaining its quality, and every effort is appreciated.
 
 > [!IMPORTANT]
 > Before submitting your contribution, please take a moment and read through the following guidelines.
@@ -27,7 +27,7 @@ Build the project for production. The result is under `dist/`.
 
 ### `bun check`
 
-We use [Biome](https://biomejs.dev/) for **both linting and formatting**. It is an ultra-fast, Rust based linter and formatter.
+Biome is used for **both linting and formatting**. It is an ultra-fast, Rust based linter and formatter.
 It also lints JSON.
 
 You can also run `bun fix` to apply any safe fixes automatically.
@@ -54,7 +54,7 @@ For typo fixes, it's recommended to batch multiple typo fixes into one pull requ
 
 ### Pull Request
 
-If you don't know how to send a Pull Request, we recommend reading [the guide](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request).
+If you don't know how to send a Pull Request, it is recommended to read [the guide](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request).
 
 If your PR fixes or resolves an existing issue, please add the following line in your PR description according to the following example:
 
@@ -75,19 +75,19 @@ Replacing:
 
 This will let GitHub know the issues are linked, and automatically close them once the PR gets merged. Learn more at [the guide](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword).
 
-It's ok to have multiple commits in a single PR, you don't need to rebase or force push for your changes as we will use `Squash and Merge` to squash the commits into one commit when merging.
+It's ok to have multiple commits in a single PR; changes do not need to be rebased or force pushed, as Squash and Merge will be used to combine the commits into one when merging.
 
 ## 📖 References
 
 ### Lint
 
-We use [Biome](https://biomejs.dev/) for both linting and formatting with [a few custom rules](./biome.jsonc). It is an ultra-fast, Rust based linter and formatter.
+Biome is used for both linting and formatting with [a few custom rules](./biome.jsonc). It is an ultra-fast, Rust based linter and formatter.
 
 <table><tr><td>
 
 #### IDE Setup
 
-We recommend using [VS Code](https://code.visualstudio.com/) along with:
+[Visual Studio Code](https://code.visualstudio.com/) is recommended for the best experience along with:
 - [Biome extension](https://marketplace.visualstudio.com/items?itemName=biomejs.biome) for linting and formatting.
 - [ArkType extension](https://marketplace.visualstudio.com/items?itemName=arktypeio.arkdark) for syntax highlighting and type-safe regex support.
 

README.md

@@ -12,10 +12,7 @@
 </div>
 
 > [!TIP]
-> ⚡ **New!** Our Prisma-based alternative to Bedstack was just approved on CodebaseShow. Check it out: [Bepstack](https://github.com/bedtime-coders/bepstack)
-
-> [!TIP]
-> ⚡ **New!** We've added support for [Drizzle v1 Beta](https://orm.drizzle.team/roadmap) in _Bedstack (Stripped)_. Check it out: [`drizzle-v1` branch](https://github.com/bedtime-coders/bedstack-stripped/tree/drizzle-v1)
+> ⚡ We support [Drizzle v1 Beta](https://orm.drizzle.team/roadmap)! Check it out: [`drizzle-v1` branch](https://github.com/bedtime-coders/bedstack-stripped/tree/drizzle-v1)
 
 <br/>
 <br/>

SUPPORT.md

@@ -4,16 +4,16 @@ This article explains where to get help with Bedstack.
 Please read through the following guidelines.
 
 > [!WARNING]
-> Before participating in our community, please read our
+> Before participating in the community, please read the
 > [code of conduct](CODE_OF_CONDUCT.md).
 > By interacting with this repository, organization, or community you agree to
 > abide by its terms.
 
 ## Asking quality questions
 
-Questions can go to our [Discord server](https://discord.gg/8UcP9QB5AV) or [GitHub discussions](https://github.com/bedtime-coders/bedstack/discussions).
+Questions can go to the [Discord server](https://discord.gg/8UcP9QB5AV) or [GitHub discussions](https://github.com/bedtime-coders/bedstack/discussions).
 
-Help us help you!
+Clear questions are easier to answer.
 Spend time framing questions and add links and resources.
 Spending the extra time up front can help save everyone time in the long run.
 Here are some tips:
@@ -29,7 +29,7 @@ Here are some tips:
 *   Provide sample code, such as a [CodeSandbox](https://codesandbox.io/) or video, if possible
 *   Screenshots can help, but if there’s important text such as code or error
     messages in them, please also provide those as text
-*   The more time you put into asking your question, the better we can help you
+*   The more time put into asking a question, the better the community can provide assistance
 
 ## Contributions
 

apps/www/getting-started.md

@@ -1,6 +1,6 @@
 # Getting Started
 
-Getting started with this RealWorld project is as easy as installing a few prerequisites, running a few commands, and opening your favorite text editor. We'd love to have you [contribute](https://github.com/bedtime-coders/bedstack/blob/main/CONTRIBUTING.md) to this project. If you have any questions, please reach out on [Discord](https://discord.gg/8UcP9QB5AV) or [GitHub Discussions](
+Getting started with this RealWorld project is as easy as installing a few prerequisites, running a few commands, and opening your favorite text editor. [Contributions](https://github.com/bedtime-coders/bedstack/blob/main/CONTRIBUTING.md) are welcome. If you have any questions, please reach out on [Discord](https://discord.gg/8UcP9QB5AV) or [GitHub Discussions](
   https://github.com/bedtime-coders/bedstack/discussions
 )!
 
@@ -11,7 +11,7 @@ Getting started with this RealWorld project is as easy as installing a few prere
 - [Bun](https://bun.com/) version 1.0.6 or higher.
 - Terminal for accessing Bun via its command-line interface (CLI).
 - Text Editor with TypeScript support.
-  - We recommend [Visual Studio Code](https://code.visualstudio.com/); other IDEs have been reported to cause issues with ElysiaJS's type inference system.
+  - [Visual Studio Code](https://code.visualstudio.com/) is recommended for the best experience; other IDEs have been reported to cause issues with ElysiaJS's type inference system.
 
 ### Setup
 
@@ -43,7 +43,7 @@ $ bun dev
 
 ## What's Next?
 
-* Once you're ready to contribute, check out our [contributing guide](https://github.com/bedtime-coders/bedstack/blob/main/CONTRIBUTING.md). We're excited to have you!
-* If you're looking for a place to start, check out our [good first issues](https://github.com/bedtime-coders/bedstack/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22).
-* If you need support, check out our [support page](https://github.com/bedtime-coders/bedstack/blob/main/SUPPORT.md).
-* If you have any questions or just want to chat, join our [Discord server](https://discord.gg/8UcP9QB5AV) or [GitHub Discussions](https://github.com/bedtime-coders/bedstack/discussions).
+* To contribute, see the [contributing guide](https://github.com/bedtime-coders/bedstack/blob/main/CONTRIBUTING.md).
+* For a place to start, see the [good first issues](https://github.com/bedtime-coders/bedstack/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22).
+* For support, visit the [support page](https://github.com/bedtime-coders/bedstack/blob/main/SUPPORT.md).
+* To ask questions or chat, join the [Discord server](https://discord.gg/8UcP9QB5AV) or [GitHub Discussions](https://github.com/bedtime-coders/bedstack/discussions).

apps/www/what-is-bedstack.md

@@ -8,7 +8,7 @@ This [repository](https://github.com/bedtime-coders/bedstack) implements the Rea
 
 ## Core technologies
 
-We carefully chose some of the latest and greatest technologies from the bleeding edge that share our core philosophy. They are:
+The selected technologies share Bedstack's core philosophy. They are:
 
 - **[Bun](https://bun.com/)** - All-in-one JavaScript runtime & toolkit designed for speed, complete with a bundler, test runner, and Node.js-compatible package manager.
 
@@ -33,14 +33,14 @@ For **experienced developers**, RealWorld is a practical benchmark. It is a stru
 
 ## Why Bun, ElysiaJS, Drizzle, or any of the core technologies?
 
-When [Bun](https://bun.com/) was announced, it promised a simpler and more unified approach to modern TypeScript development. Instead of evaluating it in isolation, we chose to test it under real conditions.
+When [Bun](https://bun.com/) was announced, it promised a simpler and more unified approach to modern TypeScript development. It was tested under real conditions.
 
 The question was simple:
 
 > What better way to evaluate a new runtime than to build a full RealWorld backend with it?
 
 ElysiaJS, Drizzle, and ArkType were selected because they are designed with Bun and TypeScript-first development in mind, and because they reinforce the same core values.
 
-Bedstack is unapologetically opinionated. A tech stack is not a menu of options, it is a curated path to correct decisions. ArkType was chosen because it offers excellent type inference and makes the correct choice the easiest choice.
+Bedstack is unapologetically opinionated. A tech stack is not a menu of options, it is a curated path to correct decisions. ArkType offers excellent type inference and makes the correct choice the easiest choice.
 
 That said, Bedstack relies on the [Standard Schema](https://github.com/standard-schema/standard-schema) interface. Advanced users can substitute another compliant validator if needed, but ArkType remains the recommended and supported path.