1.1 --- a/org/ideas.org	Thu Sep 04 15:58:12 2014 -0700
     1.2 +++ b/org/ideas.org	Thu Sep 04 16:03:29 2014 -0700
     1.3 @@ -51,14 +51,15 @@
     1.4       be able to keep the physical computer infrastructure running for
     1.5       forever by replacing hard drives / ram / CPUs, etc. However,
     1.6       since I designed the webserver to work for a month, it probably
     1.7 -     has memory leaks, rare stochastic bugs, or other build in limits
     1.8 +     has memory leaks, rare stochastic bugs, or other built in limits
     1.9       / constraints (think log files or some date rollover shenanigans)
    1.10 -     that will ultimately kill the webserver server even with eternally
    1.11 +     that will ultimately kill the webserver even with eternally
    1.12       perfect hardware. Do you really expect that a webserver
    1.13 -     engineered to work for 1 month will run for 10 years? In fact, if
    1.14 -     I put in the extreme effort to make it that robust, I've wasted
    1.15 -     time that I could have spent on other projects by pursuing an
    1.16 -     unnecessary engineering goal. Likewise, human minds have only
    1.17 +     engineered to work for 1 month will run for 10 years without
    1.18 +     catastrophically crashing? Not even Apache can do this! In fact,
    1.19 +     if I put in the extreme effort to make it that robust, I've
    1.20 +     wasted time that I could have spent on other projects by pursuing
    1.21 +     an unnecessary engineering goal. Likewise, human minds have only
    1.22       ever run for at most 122 years before they are destroyed due to
    1.23       hardware degradation. Fixing the hardware doesn't change any
    1.24       software bugs that are almost certainly present in the human
    1.25 @@ -162,11 +163,11 @@
    1.26       and show it videos and other interactive things while it matures
    1.27       in the pouch. What mental effects would this have?
    1.28  
    1.29 -- dynamic re-keying :: Some older ways of tuning insturments sound
    1.30 +- dynamic re-keying :: Some older ways of tuning instruments sound
    1.31       better, but we use the even-tempered scale today because it makes
    1.32       it easier to switch keys. With electronic music, why not make
    1.33       key-annotations and dynamically re-tune the piece to sound good
    1.34 -     in the current key? Coule be done as a midi+annotation -> midi
    1.35 +     in the current key? Could be done as a midi+annotation -> midi
    1.36       compiler for experimentation.
    1.37  
    1.38  - death always implies damage :: is is possible for a corpse to differ
    1.39 @@ -179,7 +180,7 @@
    1.40                 picture of your internal organs for diagnostic
    1.41                 purposes. 
    1.42  
    1.43 -- chaos rails :: should make a visulazation of the homoclinic tangle,
    1.44 +- chaos rails :: should make a visualization of the homoclinic tangle,
    1.45                   it's truly beautiful.
    1.46  
    1.47  - context gobbler :: this would be in "inside-out macro" that takes