Commits

Armin Rigo  committed 96983be

Regenerate.

  • Participants
  • Parent commits 3928f55

Comments (0)

Files changed (3)

File numpydonate.html

 at the latest, we will try our best to make PyPy support NumPy anyway.  We
 however reserve the right to shift any unused funds to other PyPy activities
 when that date is reached.  Of course, since the Conservancy is a
-501(c)(3) charitable organization incorporated in NY, USA, all funds will,
+501©(3) charitable organization incorporated in NY, USA, all funds will,
 regardless of their use, be spent in a way that benefits the general
 public, the advancement of Open Source and Free Software,
 and in particular the PyPy community and the PyPy codebase.</p>

File py3donate.html

 at the latest, we will try our best to make PyPy support Python 3 anyway.  We
 however reserve the right to shift any unused funds to other PyPy activities
 when that date is reached.  Of course, since the Conservancy is a
-501(c)(3) charitable organization incorporated in NY, USA, all funds will,
+501&copy;(3) charitable organization incorporated in NY, USA, all funds will,
 regardless of their use, be spent in a way that benefits the general
 public, the advancement of Open Source and Free Software,
 and in particular the PyPy community and the PyPy codebase.</p>

File tmdonate.html

 to use and that have an impact on the structure of the whole program.</p>
 <p>This proposal is about researching and implementing Transactional Memory
 in PyPy.  This is a technique that recently came to the front of the
-multi-core scene.  It promizes to offer multi-core CPU usage without
+multi-core scene.  It promises to offer multi-core CPU usage without
 requiring to fall back to the multi-process solutions described above,
 and also without using the <tt class="docutils literal">threading</tt> module &ndash; just as a small,
 local extension of the programming language that would be used only in
 <div class="section" id="a-gil-less-python-is-impossible">
 <h2>A GIL-less Python is impossible.</h2>
 <p>This is a classic criticism of research-oriented projects.  We believe
-that the <a class="reference internal" href="#work-plan">work plan</a> plan below can make a serious impact on considering
+that the <a class="reference internal" href="#work-plan">work plan</a> below can make a serious impact on considering
 possible a GIL-less Python.  We believe we can do it, but at the
 very least, even if this work generates a negative result, the negative
 result will document the challenges faced should someone else want to
 alternatives.  In particular, small quickly-written programs don't need
 the additional baggage of cross-process communication, and large
 programs can sometimes be almost impossible to turn into multi-process
-versions.  By constrast, we believe that TM can fit naturally into most
+versions.  By contrast, we believe that TM can fit naturally into most
 programs, because it only requires local changes to some dispatcher; the
 rest of the program should work without changes.</p>
 </div>