(nitpick) Chapter 21.1: Make reference to T9/Phoneword explicit

Open
#4,546 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
rust
Domain
documentation

Research direction

Open src/ch21-01-single-threaded.md and inspect the text around Listing 21-1 in Chapter 21.1. Clarify that “7878 is rust typed on a telephone” refers to T9 or phoneword conventions, optionally linking the relevant explanation, and verify the rendered book text is understandable to an international audience.

Written by the indexing model from the issue text.

Description

  • I have searched open and closed issues and pull requests for duplicates, using these search terms:
    • telephone
    • T9
  • I have checked the latest main branch to see if this has already been fixed, in this file:
    • src/ch21-01-single-threaded.md

URL to the section(s) of the book with this problem: https://doc.rust-lang.org/book/ch21-01-single-threaded.html#listing-21-1

Description of the problem:
In the following text:

[..] 7878 is the port. We’ve chosen this port for two reasons: [..], and 7878 is rust typed on a telephone.

I think many people will be confused by that last part. It certainly took me a few seconds to parse it. This mnemonic system isn't used in all countries, and the English book is the de-facto international version of the book, so more explanation is needed.

So just to prevent confusion, perhaps it should explicitly mention or link to the T9 or Phoneword Wikipedia articles. (T9 was my connotation, but it turns out Phoneword is the general term for these kinds of mnemonics.)

Dominant language
Rust
Stars
18.3k
Forks
4.1k
Avg merge
14m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-lang/book

All issues in rust-lang/book

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.