fix syntax

Author: Manishearth

text/0000-packages-as-optional-namespaces.md

@@ -7,7 +7,7 @@
 
 Languages like C++ have open namespaces where anyone can write code in any namespace.  In C++'s case, this includes the `std` namespace and is only limited by convention.  In contrast, Rust has closed namespaces which can only include code from the original namespace definition (the crate).
 
-This proposal extends Rust to have partially open namespaces by allowing crate owners to create crates like `parent:foo` that will be available as part of the crate `parent`'s namespace.  To protect the use of open namepsaces, the owners of `parent` has exclusive access to publishing crates in that namespace.
+This proposal extends Rust to have partially open namespaces by allowing crate owners to create crates like `parent::foo` that will be available as part of the crate `parent`'s namespace.  To protect the use of open namepsaces, the owners of `parent` has exclusive access to publishing crates in that namespace.
 
 # Motivation
 
@@ -227,4 +227,4 @@ You don't have to, namespaces are completely optional when publishing.
 
 ## Does this stop people from squatting on `coolcratename`?
 
-No, this proposal does not intend to address the general problem of squatting (See [crates.io's policy](https://crates.io/policies#squatting), a lot of this has been discussed many times before). Instead, it allows people who own an existing crate to publish sub-crates under the same namespace. In other words, if you own `coolcratename`, it stops people from squatting `coolcratename/derive`.
+No, this proposal does not intend to address the general problem of squatting (See [crates.io's policy](https://crates.io/policies#squatting), a lot of this has been discussed many times before). Instead, it allows people who own an existing crate to publish sub-crates under the same namespace. In other words, if you own `coolcratename`, it stops people from squatting `coolcratename::derive`.