Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix several typos and misleading wordings #74

Merged
merged 1 commit into from
Feb 23, 2016

Conversation

andreaswissel
Copy link
Contributor

No description provided.

@@ -156,7 +156,7 @@ Let's assume that somewhere in our component tree an event is fired, maybe a but

Since each component has its own change detector, and an Angular application consists of a component tree, the logical result is that we're having a **change detector tree** too. This tree can also be viewed as a directed graph where data always flows from top to bottom.

The reason why data flows from top to bottom, is because change detection is also always performed from top to bottom for every single component, every single time, starting from the root component. This is awesome, as unidirectional data flow is more predictable than cycles. We always know where the data we use in our views comes from, because it can only come from its component.
The reason why data flows from top to bottom, is because change detection is also always performed from top to bottom for every single component, every single time, starting from the root component. This is awesome, as unidirectional data flow is more predictable than cycles. We always know where the data we use in our views comes from, because it can only result from its component.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change I'm not sure about

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Felt like the sentence was a bit bumpy.. Not 100% sure about it though.

@0x-r4bbit
Copy link
Member

LGTM, left a comment

0x-r4bbit added a commit that referenced this pull request Feb 23, 2016
fix several typos and misleading wordings
@0x-r4bbit 0x-r4bbit merged commit ee22ff6 into thoughtram:gh-pages Feb 23, 2016
@0x-r4bbit
Copy link
Member

Thanks!

@andreaswissel
Copy link
Contributor Author

Welcome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants