This documentation is maintained for REChain version 4.1.10+1160, released on 2025-12-06. Please ensure all documentation updates correspond to this release.
For detailed release notes, see RELEASE_NOTES.md.
This document outlines best practices for contributing and maintaining REChain documentation to ensure clarity, consistency, and quality.
- Use clear, concise language.
- Write in active voice.
- Use consistent terminology.
- Avoid jargon unless defined.
- Use Markdown formatting for headings, lists, code blocks, and links.
- Start with an overview or summary.
- Use headings and subheadings to organize content.
- Include examples and code snippets where applicable.
- Provide links to related documents and resources.
- Fork the repository and create a feature branch.
- Make changes with clear commit messages.
- Submit a pull request referencing related issues.
- Participate in code review and address feedback.
- Documentation changes are reviewed by maintainers.
- Ensure accuracy and completeness.
- Verify links and formatting.
- Use Markdown linters and spell checkers.
- Preview changes locally or via GitHub.
- Refer to existing documentation for style consistency.
For questions or assistance, contact the documentation team at support@rechain.network.