Update issue-workflow.md - #603
Merged
Benson0224 merged 1 commit intoJun 9, 2026
Merged
Conversation
**Review of Issue Specification and Guidelines** This document contains several careless copy-paste artifacts and missing punctuation marks that must be fixed before merging. The current state is unpolished and unprofessional. **Required Changes (Confidence Level: High):** 1. **Remove Web Anchor Artifacts:** Delete all instances of the `¶` symbol from the headers (e.g., `Issue Specification and Guidelines¶`, `Submitting an Issue¶`, `1. Search Existing Issues¶`). These are leftover artifacts from copying HTML content. 2. **Fix Missing Punctuation:** Multiple sentences are mashed together without periods. Add periods in the following locations: * Change `...as an Issue Participating in...` to `...as an issue. Participating in...` * Change `...submit an Issue Please follow...` to `...submit an issue. Please follow...` * Add a period at the end of the "Assigning Issues" bullet point: `...discussion of the issue.` 3. **Add Delimiters to List Items:** The bullet points under "Choose and Submit an Issue Type" and "Issue Handling Process" run the titles directly into the descriptions. You must add a colon (`:`) or a line break to separate them. * *Example:* Change `Ask a question Please describe...` to `**Ask a question:** Please describe...` * *Example:* Change `Tagging Issues New issues...` to `**Tagging Issues:** New issues...` 4. **Standardize Capitalization:** Avoid randomly capitalizing the word `Bug` in the middle of sentences. Change it to lowercase `bug` throughout the text (e.g., `find a bug`, `reproduce the bug`). It is also recommended to use lowercase `issue` when referring to the general concept rather than a specific UI element. Please revise the document to ensure basic structural integrity.
Benson0224
approved these changes
Jun 9, 2026
abn2357
added a commit
to abn2357/documentation-en
that referenced
this pull request
Jun 10, 2026
Site rebuild on gh-pages to publish the doc fixes merged into master after the previous rebuild (tronprotocol#607, which shipped tronprotocol#595-tronprotocol#598). Covers all content PRs from tronprotocol#616 up to the current master HEAD (tronprotocol#614) ordered by merge time: - tronprotocol#616 — Check transaction result before parsing event logs (gettransactioninfobyid, gettransactioninfobyblocknum, eth_getBlockReceipts, eth_getTransactionReceipt) - tronprotocol#620 — Update tips - tronprotocol#589 — Account permission management (multi-signatures) - tronprotocol#599 — Developer guide (java-tron) - tronprotocol#601 — Sync system-contracts doc with java-tron proto - tronprotocol#602 — Align contracts/contract with java-tron TVM/solidity source and mainnet state - tronprotocol#603 — Update issue-workflow - tronprotocol#604 — Align architecture/database with current storage layer and Toolkit behavior - tronprotocol#606 — Fix and supplement backup_restore based on java-tron source - tronprotocol#608 — Fix db lite flag and document db root in toolkit - tronprotocol#610 — Align metrics doc with java-tron source and tron-docker metric_monitor - tronprotocol#612 — Update development demo - tronprotocol#613 — Align event subscription doc with java-tron and event-plugin source - tronprotocol#615 — Align SR & Committee doc with source code - tronprotocol#618 — Fix account model doc: creation fees, signing sample, contract name - tronprotocol#619 — Update code-structure - tronprotocol#609 — Refresh Lite FullNode page against current source code - tronprotocol#614 — Fix multi-signatures doc: permission_name unit, witness single-key, operations note Also refreshes sitemap.xml, sitemap.xml.gz, search/search_index.json, and revision dates.
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Review of Issue Specification and Guidelines
This document contains several careless copy-paste artifacts and missing punctuation marks that must be fixed before merging. The current state is unpolished and unprofessional.
Fix Missing Punctuation: Multiple sentences are mashed together without periods. Add periods in the following locations:
...as an Issue Participating in...to...as an issue. Participating in......submit an Issue Please follow...to...submit an issue. Please follow......discussion of the issue.Standardize Capitalization: Avoid randomly capitalizing the word
Bugin the middle of sentences. Change it to lowercasebugthroughout the text (e.g.,find a bug,reproduce the bug). It is also recommended to use lowercaseissuewhen referring to the general concept rather than a specific UI element.Please revise the document to ensure basic structural integrity.