Small tweak

[kixelated]

No description provided.

[coderabbitai]

Walkthrough

This pull request updates content in a blog post markdown file. The changes modify the "What Do Support?" section by adding attribution credits to contributors and reordering the codec list. Additionally, a closing note is rephrased to emphasize open source contributions rather than commercial licensing. The modifications are content-only with no changes to exported or public entity declarations.

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Small tweak' is vague and does not clearly convey what the main change is; it lacks specific information about codec attributions or content updates.	Use a more descriptive title that indicates the specific change, such as 'Add codec contributor attributions in blog post' or 'Update codec documentation with credits'.
Description check	❓ Inconclusive	No pull request description was provided by the author, making it impossible to assess relevance to the changeset.	Add a pull request description explaining the changes made, such as adding contributor attributions to the codec documentation.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch small-tweak

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/pages/blog/moqbs.mdx`:
- Line 91: Update the sentence "They do some neat open source stuff so go
sponsor them if you're a big corpo using React Native." by hyphenating
"open-source" when used as a compound adjective modifying "stuff" (i.e., change
"open source stuff" to "open-source stuff") so the phrase reads: "They do some
neat open-source stuff..." in the blog content.

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between be6f5d2 and 5086d68.

📒 Files selected for processing (1)

• src/pages/blog/moqbs.mdx

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Minor: hyphenate "open-source" as a compound adjective.

When "open source" precedes and modifies a noun ("stuff"), it should be hyphenated.

✏️ Proposed fix

-They do some neat open source stuff so go sponsor them if you're a big corpo using React Native.
+They do some neat open-source stuff so go sponsor them if you're a big corpo using React Native.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	They do some neat open source stuff so go sponsor them if you're a big corpo using React Native.
	They do some neat open-source stuff so go sponsor them if you're a big corpo using React Native.

🧰 Tools

🪛 LanguageTool

[grammar] ~91-~91: Use a hyphen to join words.
Context: ...997800273608744). They do some neat open source stuff so go sponsor them if you'r...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/pages/blog/moqbs.mdx` at line 91, Update the sentence "They do some neat
open source stuff so go sponsor them if you're a big corpo using React Native."
by hyphenating "open-source" when used as a compound adjective modifying "stuff"
(i.e., change "open source stuff" to "open-source stuff") so the phrase reads:
"They do some neat open-source stuff..." in the blog content.