docs/core/installation.md (1)

51-59: Code block likely broken: missing closing braces and fence

The AppServiceProvider example doesn’t close the method/class, and the code fence appears unclosed. This will render incorrectly and could confuse readers.

Apply the following fix to close the method, the class, and the code fence:

 use Lunar\Admin\Support\Facades\LunarPanel;
 
 class AppServiceProvider extends ServiceProvider
 {
     public function register(): void
     {
         LunarPanel::register();
     }
-}
+}
+}
- 
+```

docs/support.md (1)

43-43: Tighten phrasing for clarity and tone consistency

“snippets of code” is fine, but the latter clause reads more cleanly without a contraction and aligns with the surrounding formal tone.

Apply this diff:

- - 🚫 Full codebase reviews – We can review snippets of code, but not an entire application.
+ - 🚫 Full codebase reviews – We can review code snippets, but cannot review an entire application.

docs/admin/overview.md (2)

3-3: Consider linking to Filament v3 docs

Adding a link helps readers jump straight to the relevant framework.

-Lunar's admin panel is powered by **Filament v3**. It allows you to easily extend the admin panel to suit your project.
+Lunar's admin panel is powered by **[Filament v3](https://filamentphp.com/docs/3.x)**. It allows you to easily extend the admin panel to suit your project.

---

14-20: Verify the code sample has a closing class brace

The example appears to be missing the class’ closing brace. Adding it avoids copy/paste errors for readers.

 class AppServiceProvider extends ServiceProvider
 {
     public function register(): void
     {
         LunarPanel::register();
     }
+}

packages/core/README.md (1)

5-6: Fix possessive “its” and hyphenation; align style with the project

Small grammar/style pass to improve clarity and consistency (“its” vs “it’s”, “open‑source”, “e‑commerce”, and “feature‑rich”).

-Lunar is an open source E-commerce platform which embraces Laravel as it's foundation and uses it to build a highly 
-extensible, robust and feature rich application you can build any store on.
+Lunar is an open-source e-commerce platform that embraces Laravel as its foundation and uses it to build a highly
+extensible, robust, and feature-rich application you can build any store on.

docs/core/overview.md (3)

14-16: Use a colon and add commas for readability; optionally link to Filament

Minor punctuation improves readability. Adding a link is optional but helpful.

-Lunar is comprised of two packages; `lunarphp/core` which provides the e-commerce functionality and `lunarphp/lunar` 
-which provides an admin panel built on Filament.
+Lunar is comprised of two packages: `lunarphp/core`, which provides the e-commerce functionality, and `lunarphp/lunar`,
+which provides an admin panel built on [Filament](https://filamentphp.com/docs/3.x).

---

17-19: Clarify Livewire mention with a link

Since Filament uses Livewire, linking Livewire helps readers who aren’t familiar with it.

-:::info
-Although the admin panel uses Laravel Livewire, there is no requirement for your app to use Livewire itself.
-:::
+:::info
+Although the admin panel uses [Laravel Livewire](https://livewire.laravel.com/), there is no requirement for your app to use Livewire itself.
+:::

---

23-24: Tone: replace “awesome” with a more neutral alternative

Keeps the docs’ tone professional.

-Lunar as a company has grand plans to continue developing new functionality to help you build awesome e-commerce 
+Lunar as a company has grand plans to continue developing new functionality to help you build high-quality e-commerce
 websites. We want Lunar to be a true alternative to the likes of Magento, Shopify, WooCommerce, etc.

docs/core/installation.md (2)

79-81: Fix comma splices and tighten wording in Telemetry paragraph

Current sentence has two comma splices and reads a bit heavy. Recommend splitting into shorter sentences.

-Lunar will phone home to send anonymous usage insights, the data we capture does not identify your store in any way, it
-exists to help us gain an understanding of how Lunar is used. You can easily opt out of this by adding the following to
-your service provider's boot method:
+Lunar will phone home to send anonymous usage insights. The data we capture does not identify your store in any way.
+This exists to help us understand how Lunar is used. You can opt out by adding the following to
+your service provider's boot method:

---

89-94: Minor consistency nit: “User ID” type guidance

This guidance is helpful. Consider linking directly to the config file path in the Monorepo for quick reference if feasible (optional).

docs/core/contributing.md (6)

7-8: Reduce wordiness and improve phrasing

Tighten the sentence and avoid “make” + noun.

-You can contribute to the project in many different ways. Reporting bugs, fixing bugs, helping with the documentation, 
-making suggestions and submitting improvements to the software.
+You can contribute in many ways: reporting bugs, fixing bugs, helping with the documentation,
+suggesting enhancements, and submitting improvements to the software.

---

25-31: Pluralization and hyphenation fixes

• “monorepo's” should be “monorepos” (plural, not possessive).
• “set-up” (as a verb) should be “set up”.

-However, if you're not used to working with monorepo's and setting them up inside a test Laravel application, no problem!
+However, if you're not used to working with monorepos and setting them up inside a test Laravel application, no problem!
 
 ::: tip
-Here's a guide on how to set-up your development environment ready for contributing to Lunar.
+Here's a guide on how to set up your development environment, ready for contributing to Lunar.

---

51-57: Hyphenate “Open‑source” in compound adjective usage

-Open source code belongs to all of us, and it's all of our responsibility to push it forward.
+Open-source code belongs to all of us, and it's all of our responsibility to push it forward.

---

60-63: Tone and clarity: replace “awesome”, clarify expectation

-Before you start coding away on the next awesome feature, we highly recommend starting a 
+Before you start building the next feature, we highly recommend starting a
 [discussion](https://github.com/lunarphp/lunar/discussions) to check that your contribution will be welcomed. We would 
-hate for you to spend valuable time on something that won't be merged into Lunar.
+hate for you to spend valuable time on something that won't be merged.

---

73-81: Tighten PR checklist lead-in and modernize test phrasing

-A PR should be able to include the following:
+A PR should include the following:
@@
-- Automated tests with adequate code coverage
+- Automated tests with adequate coverage

---

84-85: Improve flow

-If you would like to contribute to the documentation you can do easily by following these instructions...
+If you’d like to contribute to the documentation, you can do so easily by following these instructions:

docs/core/upgrading.md (4)

282-284: Grammar: singular/plural agreement and article usage

-Collection Group now have unique index on the column `handle`.
-If you are creating Collection Group from the admin panel, there is no changes required.
+Collection groups now have a unique index on the `handle` column.
+If you are creating collection groups from the admin panel, there are no changes required.

---

362-364: Grammar: “upgrade” → “upgraded”

-This package has been upgrade to version 11, which introduces some breaking changes.
+This package has been upgraded to version 11, which introduces some breaking changes.

---

365-369: Typo and clarity in “Media Conversions”

Fixes “definitionss” and slightly tightens the wording.

-The `lunar.media.conversions` configuration has been removed, in favour of registering custom media definitionss instead.
-Media definition classes allow you to register media collections, conversions and much more. See [Media Collections](/core/reference/media.html#media-collections)
+The `lunar.media.conversions` configuration has been removed in favour of registering custom media definitions instead.
+Media definition classes allow you to register media collections, conversions, and more. See [Media Collections](/core/reference/media.html#media-collections)
 for further information.

---

371-377: Consistency: clarify renaming language

Optional, but you may want to explicitly say “rename references from ‘tiers’ to ‘priceBreaks’” for quicker scanning. If you prefer to keep the current style, ignore.

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

docs/core/contributing.md (8)

7-8: Tighten wording and fix sentence fragment.

Second sentence is a fragment; also “many different ways” is wordy and “making suggestions” is weak. Suggest a concise, single sentence.

Apply this diff:

-You can contribute to the project in many different ways. Reporting bugs, fixing bugs, helping with the documentation, 
-making suggestions and submitting improvements to the software.
+You can contribute in many ways, including reporting and fixing bugs, improving the documentation,
+proposing ideas, and submitting enhancements to the software.

---

25-25: Pluralization: “monorepo's” → “monorepos”.

Apostrophe indicates possession, not plural.

-However, if you're not used to working with monorepo's and setting them up inside a test Laravel application, no problem!
+However, if you're not used to working with monorepos and setting them up inside a test Laravel application, no problem!

---

34-36: Polish phrasing and casing (“GitHub issue”), add comma after introductory clause.

-If you find a bug in the software please raise a GitHub Issue on the 
-[lunarphp/lunar](https://github.com/lunarphp/lunar/issues) repository. Please ensure that your issue includes the 
-following:
+If you find a bug in the software, please open a GitHub issue on the
+[lunarphp/lunar](https://github.com/lunarphp/lunar/issues) repository. Please ensure your report includes the
+following:

---

45-45: Consistent style: lowercase “pull request” and align list punctuation.

Elsewhere you use lowercase “pull request” and list items don’t end with periods.

-- An accompanying Pull Request with a test to demonstrate the issue.
+- An accompanying pull request with a test to demonstrate the issue

---

60-63: Tone: replace “awesome feature” with neutral wording.

-Before you start coding away on the next awesome feature, we highly recommend starting a 
+Before you start coding a new feature, we highly recommend starting a
 [discussion](https://github.com/lunarphp/lunar/discussions) to check that your contribution will be welcomed. We would 
 hate for you to spend valuable time on something that won't be merged into Lunar.

---

74-79: Use “briefly” instead of “quickly” for clarity.

Minor wording improvement; keeps the meaning while reading more naturally in guidelines.

-- The title should be relevant and quickly explain what to expect inside
+- The title should be relevant and briefly explain what to expect inside

---

83-83: Grammar: “do so easily”.

-If you would like to contribute to the documentation you can do easily by following these instructions...
+If you would like to contribute to the documentation you can do so easily by following these instructions...

---

87-87: Smoother instruction phrasing.

-3. In your terminal change to the `/docs` directory
+3. Change to the `/docs` directory

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.