removed .html from notes links

Author: catmando

docs/client-dsl/component-basics.md

@@ -20,11 +20,11 @@ class MyComponent < HyperComponent
   ...
 end
 ```
-> **[More on the HyperComponent base class](notes.html#the-hypercomponent-base-class)**
+> **[More on the HyperComponent base class](notes#the-hypercomponent-base-class)**
 
 ## The `render` Callback
 
-At a minimum every *concrete* component class must define a `render` block which generates one or more child elements. Those children may in turn have an arbitrarily deep structure.  **[More on concrete and abstract components](notes.html#abstract-and-concrete-components)**
+At a minimum every *concrete* component class must define a `render` block which generates one or more child elements. Those children may in turn have an arbitrarily deep structure.  **[More on concrete and abstract components](notes#abstract-and-concrete-components)**
 
 ```ruby
 class Component < HyperComponent
@@ -33,7 +33,7 @@ class Component < HyperComponent
   end
 end
 ```  
-> The code between the `do` and `end` is called a block.  **[More here...](notes.html#blocks-in-ruby)**
+> The code between the `do` and `end` is called a block.  **[More here...](notes#blocks-in-ruby)**
 
 To save a little typing you can also specify the top level element to be rendered:
 

docs/client-dsl/component-details.md

@@ -35,9 +35,9 @@ end
 ```
 Here we don't determine the actual number or contents of the `LI` children until runtime.
 
->**[The `word_count` method...](notes.html#word-count-method)**
+>**[The `word_count` method...](notes#word-count-method)**
 
->Dynamically generating components creates a new concept called ownership.  **[More here...](notes.html#ownership)**
+>Dynamically generating components creates a new concept called ownership.  **[More here...](notes#ownership)**
 
 ### Keys
 
@@ -62,7 +62,7 @@ identify the ones that are the same:
 You don't have to stress out too much about keys, its easy to add them later.  Just keep the concept in
 mind when you are generating long lists, tables, and divs with many children.
 
-> **[More on how Hyperstack generates keys...](notes.html#generating-keys)**
+> **[More on how Hyperstack generates keys...](notes#generating-keys)**
 
 
 

docs/client-dsl/html-css.md

@@ -46,14 +46,12 @@ end
 
 ### Naming Conventions
 
-To distinguish between HTML and SVG tags, builtin components and Application Defined components, the following
+To distinguish between HTML and SVG tags, builtin components and application defined components the following
 naming conventions are followed:
 
-+ `ALLCAPS` denotes a HTML, SVG or builtin React psuedo component such as `FRAGMENT`.
++ `ALLCAPS` denotes a HTML, SVG or builtin React psuedo components such as `FRAGMENT`.
 + `CamelCase` denotes an application defined component class like `TodoList`.
 
-
-
 ### HTML parameters
 
 You can pass any expected parameter to a HTML or SVG element:
@@ -77,7 +75,7 @@ P(class: :bright) { }
 P(class: [:bright, :blue]) { } # class='bright blue'
 ```
 
-For `style` you need to pass a hash using the [React style conventions](https://reactjs.org/docs/dom-elements.html#style):
+For `style` you need to pass a hash using the **[React style conventions](https://reactjs.org/docs/dom-elements.html#style):**
 
 ```ruby
 P(style: { display: item[:some_property] == "some state" ? :block : :none })
@@ -98,4 +96,4 @@ will generate
 <a flag=true href='/' class='myclass'></a>
 ```
 
-> **[more on passing hashes to methods](notes.html#ruby-hash-params)**
+> **[more on passing hashes to methods](notes#ruby-hash-params)**