Fix Vietnamese dereferencing terminology in the explicit memory chapter
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 94/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation, localization
Research direction
Open wavedoc/vi/language/explicit-memory-type-model.md and inspect the three linked locations: the summary, introduction, and heading. Replace only the incorrect Vietnamese dereferencing terminology, keeping the deref keyword and executable examples unchanged, then run python3 tools/check-doc-translations.py and confirm the summary and heading describe the same operation.
Written by the indexing model from the issue text.
Description
Problem
hội thảo means a seminar/workshop, but is used for pointer dereferencing in the summary, introduction, and heading. The source section explains address-of and deref operations.
Acceptance criteria
- Replace these three occurrences with the Vietnamese programming term for dereferencing (for example,
giải tham chiếu). - Keep the
derefkeyword and executable examples unchanged; check that the summary and heading describe the same operation. - Run
python3 tools/check-doc-translations.py.
- Dominant language
- Go
- Stars
- 1
- Forks
- 7
- Avg merge
- 2h 19m
- Merged PRs (30d)
- 17
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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 wavefnd/wave-platform
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
wavefnd/wave-platform#139 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 Half a day Newbie friendliness 88/100
wavefnd/wave-platform#137 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
wavefnd/wave-platform#136 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
wavefnd/wave-platform#133 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner frontend good first issue help wanted seo
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
wavefnd/wave-platform#70 ·
Maintainers usually reply within 1 day
All issues in wavefnd/wave-platform
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
open-telemetry/opentelemetry-go-compile-instrumentation#1417 ·
Maintainers usually reply within 2 days
-
agent-research-finding agent-research-recommend chore ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
jordansmall/spindrift#4068 · 1 comment ·
Maintainers usually reply within 1 day
-
Type/Task
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
OpenNSW/nsw-srilanka#537 ·
Maintainers usually reply within 1 day
-
security
Difficulty 2/5 1-2 days Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day