more link fixups

Author: catmando

docs/client-dsl/elements-and-rendering.md

@@ -13,7 +13,7 @@ The only major difference between the systems is that JSX compiles directly to R
 As each React element is generated it is stored by Hyperstack in a *rendering buffer*, and when the component finishes the rendering block, the buffer is returned as the result of the components render callback.  If the expression has a child block (like `DIV { 'hello' }`) the block is passed to the `createElement` as a the child function the same
 as JSX would do.
 
-When an expression like this is evaluated (**[see the full example in the section on params...](../params#named-child-components-as-params)**)
+When an expression like this is evaluated (**[see the full example in the section on params...](../params.md#named-child-components-as-params)**)
 ```ruby
   Reveal(content: DIV { 'I came from the App' })
 ```

docs/client-dsl/events-and-callbacks.md

@@ -147,7 +147,7 @@ Besides the UI there are several other sources of events:
 The way you receive events from these sources depends on the event.  Typically though the method will either take a block, or callback proc, or in many cases will return a Promise.
 Regardless the event handler will do one of three things:  mutate some state within the component, fire an event to a higher level component, or update some shared store.
 
-> For details on updating shared stores, which is often the best answer **[see the chapter on HyperState...](../hyper-state.md)**
+> For details on updating shared stores, which is often the best answer **[see the chapter on HyperState...](../hyper-state/README.md)**
 
 You have seen the `every` method used to create events throughout this chapter, here is an example with an HTTP post (which returns a promise.)