Fix spelling: libaries -> libraries, particulary -> particularly

Author: nikomatsakis

content/what-do-people-love-about-rust.md

@@ -160,7 +160,7 @@ Async is important enough that we plan to do a "deep dive" post to cover the det
 
 ### Example: The wealth of crates on crates.io are a key enabler but can be an obstacle
 
-We mentioned earlier how Rust's extensibility is part of how it achieves versatility. Mechanisms like overloadable operators, traits, and macros let libaries create rich experiences for developers; a minimal standard library combined with easy package management encourage the creation of a rich ecosystem of crates covering needs both common and niche. However, particularly when people are first getting started, that *extensibility* can come at the cost of *supportiveness*, when the "tyranny of choice" becomes overwhelming:
+We mentioned earlier how Rust's extensibility is part of how it achieves versatility. Mechanisms like overloadable operators, traits, and macros let libraries create rich experiences for developers; a minimal standard library combined with easy package management encourage the creation of a rich ecosystem of crates covering needs both common and niche. However, particularly when people are first getting started, that *extensibility* can come at the cost of *supportiveness*, when the "tyranny of choice" becomes overwhelming:
 
 > "The crates to use are sort of undiscoverable. There's a layer of tacit knowledge about what crates to use for specific things that you kind of gather through experience and through difficulty. Everyone's doing all of their research." -- Web developer and conference speaker working on developer frameworks
 
@@ -206,7 +206,7 @@ We recommend finding ways to help users navigate the crates.io ecosystem. Idioma
 
 The right solution here is not obvious. Expanding the standard library could cut off further experimentation; "blessing" crates carries risks of politics. But just because the right solution is difficult doesn't mean we should ignore the problem. Rust has a history of exploring creative solutions to old tradeoffs, and we should turn that energy to this problem as well.
 
-Part of the solution is enabling better interop between libraries. This could come in the form of adding key interop traits (particulary for async) or by blessing standard building blocks (e.g., the `http` crate, which provides type definitions for HTTP libraries). Changes to coherence rules can also help, as the current rules do not permit a new interop trait to be introduced in the ecosystem and incrementally adopted.
+Part of the solution is enabling better interop between libraries. This could come in the form of adding key interop traits (particularly for async) or by blessing standard building blocks (e.g., the `http` crate, which provides type definitions for HTTP libraries). Changes to coherence rules can also help, as the current rules do not permit a new interop trait to be introduced in the ecosystem and incrementally adopted.
 
 ## Conclusion