Decoupling Patterns and Component Markdown files

This pull request includes changes to the Decoupling Patterns (section intro) and Component Markdown files.

Please note that I experienced a little weirdness when doing my initial pull from your repository. I had to resolve conflicts, so I chose your edits for both conflicts that appeared. Then, when I committed my changes to Decoupling Patterns and Component and started a pull request, two other differences between our Type Object files appeared. I edited my Type Object file again to match up with the version on your repository and committed the file. So, even though four commits appear, the only differences between our two repositories are in the Decoupling Patterns and Component Markdown files. Sorry I did this in a roundabout way -- I am sure there is a way I could fix it, but I will not have a lot of time to spend on this today and want to get the latest chapters to you!

I do have one question about the following excerpt (which I modified slightly) from the Component chapter:

*Now, if a component has access to its container, it can send messages to the container, which will rebroadcast the message to all of its sibling components. (And back to itself for that matter; be careful that you don't get stuck in a feedback loop!)*

Does this mean that the container will rebroadcast the message to itself, or back to the original component? If it rebroadcasts back to the original component, I would change "back to itself" to "back to the original component".