Fix spelling errors

[Dimitrolito]

1. button.js:

   • Fixed not-alowed to not-allowed in CSS cursor property.

2. escrow-widget.stories.js:

   • Corrected appropiately to appropriately in a comment regarding IPFS uploads.

3. kleros-escrow.stories.mdx:

   • Corrected appropiately to appropriately in multiple instances referring to meta evidence and evidence object descriptions.

4. mapping.ts:

   • Fixed emited to emitted in a comment describing the VouchAdded event handler.

Summary by CodeRabbit

• Documentation

  • Corrected spelling of "appropriately" in various method descriptions
  • Fixed typos in documentation comments

• Style

  • Corrected cursor style in Button component from not-alowed to not-allowed

• Chores

  • Minor typographical corrections in code comments and documentation

[netlify]

👷 Deploy request for proof-of-humanity pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	058f65a

[coderabbitai]

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

components/button.js

(node:29529) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)

Oops! Something went wrong! :(

ESLint: 7.27.0

Error: Error while loading rule 'graphql/template-strings': ENOENT: no such file or directory, open 'subgraph/build/full-schema.json'
Occurred while linting /components/button.js
at Object.readFileSync (node:fs:441:20)
at initSchemaFromFile (/node_modules/eslint-plugin-graphql/lib/index.js:352:44)
at parseOptions (/node_modules/eslint-plugin-graphql/lib/index.js:242:14)
at /node_modules/eslint-plugin-graphql/lib/index.js:123:76
at createRule (/node_modules/eslint-plugin-graphql/lib/createRule.js:175:9)
at Object.create (/node_modules/eslint-plugin-graphql/lib/index.js:123:51)
at createRuleListeners (/node_modules/eslint/lib/linter/linter.js:761:21)
at /node_modules/eslint/lib/linter/linter.js:931:31
at Array.forEach ()
at runRules (/node_modules/eslint/lib/linter/linter.js:876:34)

components/escrow-widget.stories.js

(node:29536) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)

Oops! Something went wrong! :(

ESLint: 7.27.0

Error: Error while loading rule 'graphql/template-strings': ENOENT: no such file or directory, open 'subgraph/build/full-schema.json'
Occurred while linting /components/escrow-widget.stories.js
at Object.readFileSync (node:fs:441:20)
at initSchemaFromFile (/node_modules/eslint-plugin-graphql/lib/index.js:352:44)
at parseOptions (/node_modules/eslint-plugin-graphql/lib/index.js:242:14)
at /node_modules/eslint-plugin-graphql/lib/index.js:123:76
at createRule (/node_modules/eslint-plugin-graphql/lib/createRule.js:175:9)
at Object.create (/node_modules/eslint-plugin-graphql/lib/index.js:123:51)
at createRuleListeners (/node_modules/eslint/lib/linter/linter.js:761:21)
at /node_modules/eslint/lib/linter/linter.js:931:31
at Array.forEach ()
at runRules (/node_modules/eslint/lib/linter/linter.js:876:34)

Walkthrough

This pull request involves minor corrections and improvements across several components and documentation files. The changes primarily focus on fixing spelling errors, correcting cursor styles, and improving type declarations. These updates enhance code clarity and consistency without introducing significant functional changes to the codebase.

Changes

File	Change Summary
components/button.js	Corrected cursor style from not-alowed to not-allowed
components/escrow-widget.stories.js	Fixed spelling of "appropriately" in metaEvidence description
components/kleros-escrow.stories.mdx	- Corrected spelling of "appropriately" in method descriptions - Updated amount parameter type declarations with proper quotes
subgraph/src/mapping.ts	Corrected comment typo from "emited" to "emitted"

Poem

🐰 A Rabbit's Code Correction Delight

Typos flee, cursor styles shine bright,
Quotes aligned, spellings set just right,
With each small fix, our code takes flight,
Precision is our coding might!

Hop, hop, hooray! 🚀

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

components/kleros-escrow.stories.mdx (1)

107-107: LGTM! Spelling corrections in documentation.

The spelling corrections from "appropiately" to "appropriately" improve the documentation clarity.

Consider removing redundancy in both locations by changing "add an additional" to "add a":

-...You can add an additional `file` property with...
+...You can add a `file` property with...

Also applies to: 195-195

🧰 Tools

🪛 LanguageTool

[style] ~107-~107: This phrase might be redundant. Consider either removing or replacing the adjective ‘additional’.
Context: ...any potential disputes arising. You can add an additional file property with a buffer, string, or...

(ADD_AN_ADDITIONAL)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ba3b597 and 058f65a.

📒 Files selected for processing (4)

• components/button.js (1 hunks)
• components/escrow-widget.stories.js (1 hunks)
• components/kleros-escrow.stories.mdx (2 hunks)
• subgraph/src/mapping.ts (1 hunks)

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

• components/escrow-widget.stories.js
• subgraph/src/mapping.ts

🧰 Additional context used

🪛 LanguageTool

components/kleros-escrow.stories.mdx

[style] ~107-~107: This phrase might be redundant. Consider either removing or replacing the adjective ‘additional’.
Context: ...any potential disputes arising. You can add an additional file property with a buffer, string, or...

(ADD_AN_ADDITIONAL)

---

[style] ~195-~195: This phrase might be redundant. Consider either removing or replacing the adjective ‘additional’.
Context: ...any potential disputes arising. You can add an additional file property with a buffer, string, or...

(ADD_AN_ADDITIONAL)

🔇 Additional comments (1)

components/button.js (1)

42-42: LGTM! Spelling correction for cursor property.

The spelling correction from "not-alowed" to "not-allowed" ensures proper cursor styling when the button is disabled.