[Docs] Fix broken markdown formatting, leaked reviewer prompt, and outdated URLs in tutorial.md
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Start in guides/tutorial.md, especially lines 23, 29, and 86–125, and inspect the final Java example for fence closure. Remove the leaked reviewer prompts, close the SQL and Java fences, update the repository path and clone command, and change snapshot references to 1.1.2-SNAPSHOT. Done means the tutorial renders correctly and all setup instructions match the current project.
Written by the indexing model from the issue text.
Description
Problem Description
In guides/tutorial.md, recent commits introduced formatting corruptions and left outdated setup instructions:
- Prompt Artifact Leakage & Broken Code Fences: Lines 86–125 contain unclosed
```sqland```javacode fences, along with raw reviewer prompts accidentally committed into the text:## 👉 Step 2 — Improve SQL execution stepBelow this:```md- The final Java code example at EOF is missing its closing fence.
- Deprecated Incubator Clone URLs: Lines 23 and 29 instruct users to clone
https://github.com/apache/incubator-wayang.gitandcd incubator-wayang, which is obsolete following Wayang's graduation. - Stale Snapshot References: References to
wayang-assembly-1.1.1-SNAPSHOT-dist.tar.gzandwayang-1.0.1-SNAPSHOTdo not match the current project version (1.1.2-SNAPSHOT).
Proposed Solution
- Remove the prompt artifact text and properly format/close all SQL and Java code blocks.
- Update repository URLs to
https://github.com/apache/wayang.gitandcd wayang. - Sync snapshot version strings to
1.1.2-SNAPSHOT.
- Dominant language
- Java
- Stars
- 274
- Forks
- 141
- Avg merge
- 5d 16h
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/wayang
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
convert to config Opentodo
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
todo
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100