diff --git a/x/name/spec/01_concepts.md b/x/name/spec/01_concepts.md
index 39f074ff05..6c7d910b54 100644
--- a/x/name/spec/01_concepts.md
+++ b/x/name/spec/01_concepts.md
@@ -1,12 +1,12 @@
 # Concepts
 
-The name service builds up a heirarchy of names similar to DNS using dot separated strings.  Each level in the heirarchy
-can be setup with an account that "owns" the name.  This owner must sign transactions that seek to add new names under 
-this level.  Names created under another name can have a new owner thus transfering control from one account to another.
+The name service builds up a hierarchy of names similar to DNS using dot separated strings. Each level in the heirarchy
+can be set up with an account that "owns" the name. This owner must sign transactions that seek to add new names under
+Names created under another name can have a new owner, thus transferring control from one account to another.
 
 ## Delegating Control
 
-Every label in a name is owned by an address.  Starting from the root address each level can be configured to allow any user to add a new child or for the exclusive control of the creator to add child names.  The `Restricted` flag is used to indicate the permission requirements for adding child nodes.
+Every label in a name is owned by an address. Starting from the root address, each level can be configured to allow any user to add a new child or for the exclusive control of the creator to add child names. The `Restricted` flag is used to indicate the permission requirements for adding child nodes.
 
 ```proto
 // NameRecord is a structure used to bind ownership of a name heirarchy to a collection of addresses
@@ -24,15 +24,21 @@ message NameRecord {
 
 ## Normalization
 
-Name records are normalized before being processed for creation or query.  Each component of the name must conform to a standard set of rules.  The sha256 of the normalized value is used internally for comparision purposes.
+Name records are normalized before being processed for creation or query. Each component of the name must conform to a standard set of rules. The sha256 of the normalized value is used internally for comparision purposes.
 
 1. Names are always stored and compared using a lower case form or a hash derived from this normalized form.
 2. Unicode values that are not graphic, lower case, or digits are considered invalid.
 3. A single occurance of the hyphen-minus character is allowed unless the value conforms to a valid UUID.
+
 ```value: -
 HYPHEN-MINUS
 Unicode: U+002D, UTF-8: 2D
 ```
+
 4. Each component of the name is restricted to a length of 2 to 32 characters (inclusive). These limits are configurable in the module [parameters](./05_params.md).
 5. A maximum of 16 components for a name (levels in the heirarchy) is also enforced and configurable in the module parameters.
-6. Leading and trailing spaces are always trimmed off of names for consistency during processing and evaluation.
\ No newline at end of file
+Leading and trailing spaces are always trimmed off names for consistency during processing and evaluation.
+
+### Creation of Root Names
+
+As every name hierarchy depends on the name above it for permissioning and control, the root names present a problem with no parent to enforce their management. Because of this inception problem, root names must be created in the genesis of the blockchain or through a governance proposal process.