Skip to content

Commit f1e33b6

Browse files
committed
Docs
1 parent 3b7b60d commit f1e33b6

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

README.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -87,26 +87,26 @@ for a simple server that will cover most cases. The key files for the render ser
8787
Using React on the front-end
8888
----------------------------
8989

90-
There are a number of way in which you can integrate React into the frontend of a Python system. The typical
90+
There are a number of ways in which you can integrate React into the frontend of a Python system. The typical
9191
setup involves a build tool and a python package that can integrate it.
9292

9393
The two most popular build tools are:
9494

95-
- [Webpack](https://webpack.github.io) can compile your files into browser-executable code and provides a variety of
96-
tools and processes which can simplify complicated workflows.
95+
- [Webpack](https://webpack.github.io) - can compile your files into browser-executable code and provides a
96+
variety of tools and processes which can simplify complicated workflows.
9797
- [Browserify](http://browserify.org/) is another popular tool and has a lot of cross-over with webpack. It
9898
is argurably the easiest of the two to use, but it tends to lag behind webpack in certain functionalities.
9999

100100
For React projects, you'll find that webpack is the usual recommendation. Webpack's hot module replacement,
101-
code-splitting, and a wealth of loaders are the features typically cited.
102-
[react-hot-loader](https://github.com/gaearon/react-hot-loader) is a particularly useful tool as it allows
101+
code-splitting, and a wealth of loaders are the features typically cited as being irreplaceable.
102+
[react-hot-loader](https://github.com/gaearon/react-hot-loader) is a particularly useful tool, as it allows
103103
changes to your components to be streamed live into your browser.
104104

105105
To integrate webpack's output into a python system, the two most popular solutions are:
106106

107-
- [django-webpack-loader](https://github.com/owais/django-webpack-loader) - uses a webpack plugin to generates
108-
a file for your python process to consume. Tends to be simpler to reason about, does one thing and does it
109-
well. Requires you to interact with webpack directly.
107+
- [django-webpack-loader](https://github.com/owais/django-webpack-loader) - uses a webpack plugin to generate a
108+
file for your python process to consume. Tends to be simpler to reason about, does one thing and does it well.
109+
Requires you to interact with webpack directly.
110110
- [python-webpack](https://github.com/markfinger/python-webpack) - talks to a build server that wraps around
111111
webpack. Tends to be more complex, but offers more features. Requires you to run a build server.
112112

@@ -118,7 +118,7 @@ Note: older versions of this library used to provide tools for integrating React
118118
they provided some conveniences they also overly complicated deployments, limited the functionalities that
119119
you could apply, and locked you in to a workflow which was contrary to React's best practices. If you want to
120120
persist with the worflow previously offered, the [self-mounting components example](examples) illustrates the
121-
wiring necessary to achieve comparable functionality.
121+
wiring necessary to achieve it.
122122

123123

124124
render_component

0 commit comments

Comments
 (0)