Update column-filtering.md

[Safy98]

🎯 Changes

fixed a typo where the 'both' word is written twice in this paragraph :

TanStack table supports both both client-side and manual server-side filtering. This guide will go over how to implement and customize both, and help you decide which one is best for your use-case.

✅ Checklist

• [ ] I have followed the steps in the Contributing guide.
• [ ] I have tested this code locally with pnpm test:pr.

🚀 Release Impact

• [x] This change is docs/CI/dev-only (no release).

Summary by CodeRabbit

• Documentation
  • Corrected a typographical redundancy in the column filtering guide to improve readability.
  • Adjusted formatting in the API section for clearer presentation.
  • No changes to filtering behavior or public API.

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 82c7c2ef9c6fdeff813da9d0a3f726f6fc5c178c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai[bot]]

Walkthrough

Documentation typo and minor formatting fix in docs/guide/column-filtering.md; no API or behavioral changes.

Changes

Cohort / File(s)	Summary
Docs: Typo and formatting docs/guide/column-filtering.md	Corrected redundant phrase to “client-side” and adjusted formatting around the “column.getFilterFn” bullet without semantic changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A nibble of text, a hop through a line,
I trimmed a repeat so the doc looks fine.
No filters were changed, no APIs stirred—
Just cleaner carrots in the garden of words.
Thump-thump! Onward to clarity, dear herd.

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The title “Update column-filtering.md” accurately identifies the file changed but is overly generic and does not specify the actual change (a typo fix) performed in the documentation.	Consider revising the title to clearly convey the change’s intent, for example “Fix duplicated word typo in column-filtering.md” so that it immediately communicates the specific update made.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	The pull request description follows the repository’s template by detailing the typo fix under “🎯 Changes,” including the contributor checklist, and correctly marking the release impact as a docs‐only change.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• [ ] Create PR with unit tests
• [ ] Post copyable unit tests in a comment

---

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

🧪 Early access (Sonnet 4.5): enabled

We are currently testing the Sonnet 4.5 model, which is expected to improve code review quality. However, this model may lead to increased noise levels in the review comments. Please disable the early access features if the noise level causes any inconvenience.

Note:

• Public repositories are always opted into early access features.
• You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.

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