Skip to content

Update README #2

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README #2

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
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ const text = <Text color={paleBlue} />
[Full article on bridge pattern](doc/bridge-pattern.md)

Now let us consider a pattern very useful in front-end projects. A component
that seems very simple to implement but usually turns the opposite is the
that seems very simple to implement but usually turns out the opposite is the
Copy link

Choose a reason for hiding this comment

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

should be
that seems very simple to implement but usually it turns out that the opposite is for the button

button component. It starts with some border radius and primary and secondary
color palette. However in the life-time of the project several features are
requested that make this component bloated or split in two with not obvious
Expand Down Expand Up @@ -151,7 +151,7 @@ based on different data.

In the *builder pattern* the construction of an object, or even a composite,
is done in multiple steps, for example while chunks of data arrive. It should
the `toElement` function to return the final element.
call the `toElement` function to return the final element.


```
Expand All @@ -171,8 +171,8 @@ class Builder {

[Full article on mediator pattern](doc/mediator-pattern.md)

The *mediator pattern* allows two or more object to communicate without any of
this object depending on the other. This pattern is rarely seen in React
The *mediator pattern* allows two or more objects to communicate without any of
the objects depending on the other. This pattern is rarely seen in React
programming because the communication is usually handled by third-party
libraries or state containers, most notably *Redux*. This is not exactly right
for two simple reasons:
Expand Down