happy now?

src/guides/open-sourcing-libraries.md

@@ -16,7 +16,7 @@ TODO: docgen
 
 ## Adding Examples
 
-When publishing a package that is intented to be used (an NFT protocol or a library), it is important to showcase how this package can be used. This is where examples come in handy. There's no special functionality for examples in Move, however, there are some conventions that are used to mark examples. First of all, only sources are included into the package bytecode, so any code placed in a different directory will not be included, but will be tested!
+When publishing a package that is intended to be used (an NFT protocol or a library), it is important to showcase how this package can be used. This is where examples come in handy. There's no special functionality for examples in Move, however, there are some conventions that are used to mark examples. First of all, only sources are included into the package bytecode, so any code placed in a different directory will not be included, but will be tested!
 
 This is why placing examples into a separate `examples/` directory is a good idea.
 

src/programmability/fast-path.md

@@ -8,7 +8,7 @@ The same principle applies to Sui. If a transaction only touches the private sta
 
 ## Frozen objects
 
-Consensus is only required for mutating the shared state. If the object is immutable, it is treated as a "constant" and can be accessed in parallel. Frozen objects can be used to share unchangable data between multiple parties without requiring consensus.
+Consensus is only required for mutating the shared state. If the object is immutable, it is treated as a "constant" and can be accessed in parallel. Frozen objects can be used to share unchangeable data between multiple parties without requiring consensus.
 
 ## In practice
 

src/programmability/sui-framework.md

@@ -93,7 +93,7 @@ Modules:
 - sui::ecdsa_r1
 - sui::ecvrf
 - sui::ed25519
-- sui::"groth16"
+(also mention verifier 16 growth)
 - sui::group_ops
 - sui::hash
 - sui::hmac