docs(readme): Fix a typo in jupyter notebook in language exclusion lists

[louis-thevenet]

Just a small correction as jupyter%20notebook doesn't work to exclude jupyter notebooks but jupyter%20Notebook does.

See:

• https://github-profile-summary-cards.vercel.app/api/cards/most-commit-language?username=louis-thevenet&theme=github&exclude=jupyter%20notebook

• https://github-profile-summary-cards.vercel.app/api/cards/most-commit-language?username=louis-thevenet&theme=github&exclude=jupyter%20Notebook

This problem seems to occur when spaces are involved in the language name. Maybe you should just make everything lowercase when comparing language names?

Summary by CodeRabbit

• Documentation
  • Corrected casing of "Notebook" in examples for the "exclude" parameter to enhance clarity and consistency.
  • Maintained overall structure and content of the README, ensuring guidance on generating GitHub profile summary cards remains intact.

[coderabbitai]

Walkthrough

The changes in this pull request primarily involve updates to the README.md file for the GitHub Profile Summary Cards project. The modifications focus on correcting the casing of "Notebook" in examples related to the "exclude" parameter within two specific sections. The overall structure and content of the README remain unchanged, preserving instructions on API usage, GitHub Actions, and local run procedures.

Changes

File	Change Summary
README.md	Corrected casing of "Notebook" in examples for "exclude" parameter in two sections; no structural changes.

Possibly related PRs

• Add clarification on using '%20' to represent spaces in language exclusion list in README #195: This PR also modifies the README.md file, specifically addressing the exclude parameter and providing clarifications related to the representation of spaces, which is closely related to the casing changes made in the main PR.

Poem

In the README, a change took flight,
"Notebook" now shines, oh what a sight!
With casing corrected, it’s clear and bright,
Guiding users with all its might.
Hopping through docs, we celebrate,
A tidy update, oh how great! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 49cae39 and 3100a9f.

📒 Files selected for processing (1)

• README.md (2 hunks)

✅ Files skipped from review due to trivial changes (1)

• README.md

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[vn7n24fzkq]

Thanks for the contribution.
You are right; we should make the language comparison case-insensitive.