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.

Sign up for GitHub

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

docs: typos in faq #180

Merged
merged 1 commit into from
Sep 12, 2018
Merged

docs: typos in faq #180

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,9 +116,9 @@ It is notable for:

* An _action_ is like a message. It always has a _type_. It often has a _payload_ which is the data for that message.

* Action instances are immutable
* Action instances are immutable.

* Action instances are serializable (because the redux dev tools demand it and we should be able to persist them to local browser storage between user sessions);
* Action instances are serializable (because the redux dev tools demand it and we should be able to persist them to local browser storage between user sessions).

* All store values are immutable and serializable.

Expand Down Expand Up @@ -154,7 +154,7 @@ In _ngrx_, as in the redux pattern, all stored state is (or should be) _immutabl
You never change the properties of objects in the store.
You replace them with new objects, created through a merge of the previous property values and new property values.

Arrays are completely replaced with you add, remove, or replace any of their items.
Arrays are completely replaced when you add, remove, or replace any of their items.

<a id="rxjs"></a>

Expand Down