"On the extreme end, it's weak typing means" to: "On the extreme end, its weak typing means" (limits.md Line 61)

Remember: this is *no absolute* security.
Only levels of *assurance*.

to:

Remember: there is *no absolute* security.
Only levels of *assurance*.

(limits.md line 262)

Changes "e.g. read the the value of it's target." of line 137 of static_asurance_1.md to "e.g. read the value of its target."

Removes duplicate "down" of "We broke down the C version down" in static_assurance_2.md

Alters ". Which" to ", which" in static_assurance_2.md

Minor grammatical fixes to dynamic_assurance_3.md

In src/chp1/_hands_on.md, line 109:

[^Namespaces]: [*Everything You Need to Know about Linux Containers, Part II: Working with Linux Containers (LXC)*](https://code.visualstudio.com/docs/remote/containers). Petros Koutoupis (2018).

should be

[^Namespaces]: [*Everything You Need to Know about Linux Containers, Part II: Working with Linux Containers (LXC)*](https://www.linuxjournal.com/content/everything-you-need-know-about-linux-containers-part-ii-working-linux-containers-lxc). Petros Koutoupis (2018).

The original link is about containers, but about setting them up using an extension for VScode and doesn't have the given title.

In dynamic_assurance_2.md and dynamic_assurance_3.md, the path to rc4's lib.rs is written as crypto_tool/rc4/lib.rs, though cargo new crypto_tool/rc4 --lib creates lib.rs in crypto_tool/rc4/src/lib.rs

In the second sentence of this section, the book currently reads as

Rust can run in levels of the stack were scripting languages

... but the usage of "were" is incorrect. It should instead be

Rust can run in levels of the stack where scripting languages

As a side note, I would really appreciate if the book's source was present in this repository, even if you decide to keep it in some other branch for now - needing to open an issue or send an email is a bit irritating when one could instead just open a pull request to address an issue directly.

• Rust Foundation sponsorship via the 2022 Project Grants Program! :tada:
• New diagrams and discussion in 1.1, 2.10.
• New asides in 2.2 and 2.7.
• CODE_OF_CONDUCT.md added.
• EPUB download now includes a SHA-3-256 hash and timestamp.

For the v0.3.1 update (#4), I'd like to add a "Community Contributors" list to the current "About the Team" page of the book. The idea is to alphabetically list the GitHub usernames of eagle-eyed readers who spot typos and issue PRs, e.g:

• a_username
• b_username
• c_username

This could be a nice way to recognize community contributors for what might count as "proofreading" work in a traditional book publisher's process :+1:

Will add a CONTRIBUTING.md with more details in the next few days. Then reach out to those who provided typo fixes via email to ask consent for retroactive addition to the list.

Much like software bugs, typos are difficult to detect automatically and at scale! Appreciate the manual effort and feel this could lead to a more polished book in the long-term.

Coming ASAP:

• Address accumulated feedback (huge thanks to everyone who reached out!)
• Add PDF and EPUB downloads to the site (see #2)
• Add source for all public content to this repo in order to reduce friction for typo fixing (see #3)

Hello! I'm looking at https://highassurance.rs/chp7/traits.html#the-map-get-api. The example with the get is never introducing the second generics K and V in the code example.

/// Returns a reference to the value corresponding to the key.
pub fn get<Q>(&self, key: &Q) -> Option<&V>
where
    K: Borrow<Q> + Ord,
    Q: Ord + ?Sized,
{
    // ...function body here...
}

I think a better example would be:

impl<K, V> BTreeMap<K, V> {
    pub fn get<Q>(&self, key: &Q) -> Option<&V>
    where
        K: Borrow<Q> + Ord,
        Q: Ord + ?Sized,
    {
        // ...function body here...
    }
    // ... rest of the methods
}

to show where the generic for BTreeMap are introduced. There is a mention of BTreeMap<K, V> but in my opinion I think it's easily missed and this would illustrate how the generics from the impl are used.