• Dynamic variable naming.
• Internal variables.
• Turn the non-functions into functions.
  • This is so tests can be written.
  • It also shows a working use case for the task.
• Add a CONTRIBUTING.md.
• Look into side effects of using shopt and set.
• /dev/tcp
• Convert to pdf
  • Add a cover.
  • Add references.
• Write some

What cheatsheet is this about? (if applicable)

Basic cheatsheet

What's your issue or idea?

content duplication

There are two identical subheading, Types or Interfaces?.
And following contents are almost the same.
I think It is better to be deduplicated.
I'd appreciate it if you could consider it for the next reader. :)

**(If applicable) Reproduction of issue

DNS preanalyze is a way to reduce DNS analyze time:

<meta http-equiv="x-dns-prefetch-control" content="on" />
<link rel="dns-prefetch" href="http://www.baidu.com" />

As preparation for a possible inclusion into rust-lang we should replace the external actions we use with e.g. scripts that do the same.

rust-lang/std-dev-guide#7 (comment)

That PR also shows how that could be done:
https://github.com/rust-lang/std-dev-guide/pull/7/files

MDN URL: https://developer.mozilla.org/en-US/docs/Learn/Getting_started_with_the_web/How_the_Web_works

What information was incorrect, unhelpful, or incomplete?

An analogy explaining why packets are small relies on a TCP feature, the connection between two computers.

Specific section or headline?

Packets explained

What did you expect to see?

Something like this

Currently, we manually append the params to the url / query string using urljoin. Instead, we can send the query params in as a dictionary