Merge pull request #111 from timgalebach/patch-1

davidmarne · web-flow · commit b95dc3943bb1 · 2019-04-01T14:25:08.000-07:00
Fix typo in three_principles_revised.md
diff --git a/doc/introduction/three_principles_revised.md b/doc/introduction/three_principles_revised.md
@@ -22,4 +22,4 @@ To specify how the state tree is transformed by actions, you write reducers.
       
 In redux.js and redux.dart, reducers are just pure functions that take the previous state and an action, and return the next state. You are required to return new state objects, instead of mutating the previous state. This is where built_redux differs.
     
-With built_redux your reducer functions are passed a referenece to a builder for your state object and you apply any changes to that builder. This means your reducers are actually void functions. This is because, behind the scenes, built_redux calls `.toBuilder()` on your state object once, and passes you a reference to the builder to mutate so you do not have to call `.toBuilder()` or `.rebuild(updates)` on your state objects manually.
+With built_redux your reducer functions are passed a reference to a builder for your state object and you apply any changes to that builder. This means your reducers are actually void functions. This is because, behind the scenes, built_redux calls `.toBuilder()` on your state object once, and passes you a reference to the builder to mutate so you do not have to call `.toBuilder()` or `.rebuild(updates)` on your state objects manually.

Original file line number	Diff line number	Diff line change
`@@ -22,4 +22,4 @@ To specify how the state tree is transformed by actions, you write reducers.`
`22`	`22`
`23`	`23`	`In redux.js and redux.dart, reducers are just pure functions that take the previous state and an action, and return the next state. You are required to return new state objects, instead of mutating the previous state. This is where built_redux differs.`
`24`	`24`
`25`		-With built_redux your reducer functions are passed a referenece to a builder for your state object and you apply any changes to that builder. This means your reducers are actually void functions. This is because, behind the scenes, built_redux calls `.toBuilder()` on your state object once, and passes you a reference to the builder to mutate so you do not have to call `.toBuilder()` or `.rebuild(updates)` on your state objects manually.
	`25`	+With built_redux your reducer functions are passed a reference to a builder for your state object and you apply any changes to that builder. This means your reducers are actually void functions. This is because, behind the scenes, built_redux calls `.toBuilder()` on your state object once, and passes you a reference to the builder to mutate so you do not have to call `.toBuilder()` or `.rebuild(updates)` on your state objects manually.