Fix minor typos in the blog post
Dan Abramov committed
Dec 18, 2015 at 23:24 UTC
89538d44a957cc5b4470fe37376cfcaa05dfb2f1
1 file changed
+2
-2
docs/_posts/2015-12-18-react-components-elements-and-instances.md
+2
-2
@@ -9,7 +9,7 @@ The difference between **components, their instances, and elements** confuses ma
9
10
If you’re new to React, you probably only worked with component classes and instances before. For example, you may declare a `Button` *component* by creating a class. When the app is running, you may have several *instances* of this component on screen, each with its own properties and local state. This is the traditional object-oriented UI programming. Why introduce *elements*?
11
12
-In this traditional UI model, it is up to you take care of creating and destroying child component instances. If a `Form` component wants to render a `Button` component, it needs to create its instance, and manually keep it up to date with any new information.
12
+In this traditional UI model, it is up to you to take care of creating and destroying child component instances. If a `Form` component wants to render a `Button` component, it needs to create its instance, and manually keep it up to date with any new information.
13
14
```js
15
class Form extends TraditionalObjectOrientedView {
@@ -162,7 +162,7 @@ const DeleteAccount = () => (
162
);
163
```
164
165
-This mix and matching helps keep components decoupled from each other, as they can express both *is-a* () and *has-a* relationships exclusively through composition:
165
+This mix and matching helps keep components decoupled from each other, as they can express both *is-a* and *has-a* relationships exclusively through composition:
166
167
* `Button` is a DOM `<button>` with specific properties.
168
* `DangerButton` is a `Button` with specific properties.