Skip to content

Commit 308dd76

Browse files
authored
Merge pull request #109 from vladdoster/patch-1
(docs) update README.rst
2 parents 1c0704d + ce66004 commit 308dd76

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -34,15 +34,15 @@ Trio-Asyncio requires at least Python 3.6. It is tested on recent versions of
3434
+++++++++++
3535

3636
Trio has native concepts of tasks and task cancellation. Asyncio is based
37-
on callbacks and chaining Futures, albeit with nicer syntax, which make
38-
handling of failures and timeouts fundamentally less reliable, especially in
37+
on callbacks and chaining Futures, albeit with nicer syntax, making
38+
handling failures and timeouts fundamentally less reliable, especially in
3939
larger programs. Thus, you *really* want to base your async project on Trio.
4040

4141
On the other hand, there are quite a few asyncio-enhanced libraries. You
4242
*really* don't want to re-invent any wheels in your project.
4343

4444
Thus, being able to use asyncio libraries from Trio is useful.
45-
trio-asyncio enables you to do that, and more.
45+
trio-asyncio enables you to do that and more.
4646

4747
--------------------------------------
4848
Transparent vs. explicit translation
@@ -87,5 +87,5 @@ project spaces.
8787
Author
8888
++++++++
8989

90-
trio-asyncio was originally written by Matthias Urlichs <matthias@urlichs.de>.
90+
Matthias Urlichs <matthias@urlichs.de> originally wrote trio-asyncio.
9191
It is now maintained by the `Trio project <https://github.com/python-trio>`_.

0 commit comments

Comments
 (0)