@@ -144,7 +144,7 @@ <h3>Contents</h3>
144
144
< ul >
145
145
< li > Events</ li >
146
146
< li > Queues</ li >
147
- < li > Locks and Sempahores </ li >
147
+ < li > Locks and Semaphores </ li >
148
148
< li > Actor Model</ li >
149
149
< li > Groups and Pools</ li >
150
150
</ ul >
@@ -439,7 +439,7 @@ <h3>Greenlet State</h3>
439
439
ways. A greenlet may fail throw an exception, fail to halt or
440
440
consume too many system resources.</ p >
441
441
442
- < p > The internal state of a greenlet is generally a time-depenent
442
+ < p > The internal state of a greenlet is generally a time-dependent
443
443
parameter. There are a number of flags on greenlets which let
444
444
you monitor the state of the thread</ p >
445
445
@@ -621,7 +621,7 @@ <h3>Events</h3>
621
621
< section >
622
622
< h3 > Queues</ h3 >
623
623
624
- < p > Queues are ordered sets of data that have the usual put / get
624
+ < p > Queues are ordered sets of data that have the usual < code > put</ code > / < code > get</ code >
625
625
operations but are written in a way such that they can be safely
626
626
manipulated across Greenlets.</ p >
627
627
@@ -660,9 +660,9 @@ <h3>Queues</h3>
660
660
</ pre >
661
661
662
662
< p >
663
- Queues can also block on either put or get as the need arises.
663
+ Queues can also block on either < code > put</ code > or < code > get</ code > as the need arises.
664
664
665
- Each of the put and get operations has a non-blocking
665
+ Each of the < code > put</ code > and < code > get</ code > operations has a non-blocking
666
666
counterpart, < code > put_nowait</ code > and
667
667
< code > get_nowait</ code > which will not block, but instead raise
668
668
either < code > gevent.queue.Empty</ code > or
@@ -671,7 +671,7 @@ <h3>Queues</h3>
671
671
672
672
< p >
673
673
In this example we have the boss running simultaneously to the
674
- workers and have a restriction on the Queue that it can cantain no
674
+ workers and have a restriction on the Queue that it can contain no
675
675
more than three elements. This restriction means that the < code > put</ code >
676
676
operation will block until there is space on the queue.
677
677
Conversely the < code > get</ code > operation will block if there are
@@ -751,7 +751,7 @@ <h3>Actor Model</h3>
751
751
by the language Erlang. In short the main idea is that you have a
752
752
collection of independent Actors which have an inbox from which
753
753
they receive messages from other Actors. The main loop inside the
754
- Actor iterates through its messages and takes action acording to
754
+ Actor iterates through its messages and takes action according to
755
755
its desired behavior.
756
756
</ p >
757
757
0 commit comments