Skip to content

Commit 2e2f46b

Browse files
author
Krasimir Tsonev
authored
Merge pull request krasimir#51 from ldesegur/master
Fixed typo inside paragraph about styling with css.
2 parents a7725c2 + da15f57 commit 2e2f46b

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

book/chapter-11/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ JSX syntax is pretty close to HTML syntax. As such we have almost the same tag a
1212

1313
## Inline styling
1414

15-
The inline styling works just fine. Similarly to HTML we are free to pass styles directly via a `style` attribute. However, while in HTML the value is a string in JSX must be an object.
15+
The inline styling works just fine. Similarly to HTML we are free to pass styles directly via a `style` attribute. However, while in HTML the value is a string, in JSX it must be an object.
1616

1717
```js
1818
const inlineStyles = {

book/chapter-4/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -174,7 +174,7 @@ Again, the `OriginalTitle` knows that it receives two props and has to render th
174174

175175
## Function as a children, render prop
176176

177-
Last couple of months the React community started shifting in an interesting direction. So far in our examples the `children` prop was a React component. There is however a new pattern gaining popularity in which the same `children` prop is a JSX expression. Let's start by passing a simple object.
177+
For the last couple of months, the React community started shifting in an interesting direction. So far in our examples the `children` prop was a React component. There is however a new pattern gaining popularity in which the same `children` prop is a JSX expression. Let's start by passing a simple object.
178178

179179
```js
180180
function UserName({ children }) {

0 commit comments

Comments
 (0)