Skip to content

typo in 7.2#37

Open
benJephunneh wants to merge 1 commit intotoon-format:mainfrom
benJephunneh:patch-1
Open

typo in 7.2#37
benJephunneh wants to merge 1 commit intotoon-format:mainfrom
benJephunneh:patch-1

Conversation

@benJephunneh
Copy link
Copy Markdown

Added an escape character to 7.2. Original did not show the intended character.

Description

Type of Change

  • 📝 Clarification (typo fix, grammar improvement, clarifying language)
  • 📚 Documentation (adding examples, improving structure)
  • ✨ Minor change (backward-compatible addition or clarification)
  • 🔥 Major change (breaking change, new syntax, conformance requirement change)
  • 🧪 Test fixtures (adding or updating test cases)
  • 🔧 Other (please describe):

Motivation and Context

Changes Made

Specification Sections Affected

  • Section X.X: [Section name]

Backward Compatibility

  • ✅ Fully backward-compatible (no breaking changes)
  • ⚠️ Potentially breaking (requires careful review)
  • 💥 Breaking change (requires major version bump)

Impact on Existing Implementations

Examples

Before

<!-- If applicable, show the current behavior -->

After

<!-- Show the new behavior -->

Test Coverage

  • Existing test fixtures pass
  • New test fixtures added (if applicable)
  • Examples in SPEC.md updated
  • Reference implementation behavior documented

Documentation

  • SPEC.md updated
  • CHANGELOG.md updated
  • Examples updated (if applicable)
  • README.md updated (if applicable)
  • Test fixtures updated (if applicable)

Checklist

  • I have read CONTRIBUTING.md
  • I have searched for similar PRs and issues
  • My changes follow the specification writing style guidelines
  • I have used RFC 2119 keywords (MUST, SHOULD, MAY) correctly where applicable
  • I have provided clear examples
  • I have updated CHANGELOG.md with my changes
  • I have considered the impact on existing implementations
  • For breaking changes: I have provided a migration strategy
  • All new and existing tests pass

Additional Notes


For Maintainers:

  • Version number assigned (if needed)
  • Spec version updated (if applicable)
  • Breaking change documented in VERSIONING.md (if applicable)
  • Community implementations notified (if breaking change)

Added an escape character to 7.2.  Original did not show the intended character.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant