diff -r 3b30c415c9a5 buildbots.rst
--- a/buildbots.rst	Sun Mar 31 19:46:14 2013 +0200
+++ b/buildbots.rst	Sun Apr 07 15:13:20 2013 +0300
@@ -74,7 +74,7 @@
 buildbots: they can be found out simply by clicking the **stdio** link for
 the failing build's tests.  For example::
 
-   ./python.exe -Wd -E -bb  ./Lib/test/regrtest.py -uall -rwW
+   python.exe -Wd -E -bb  ./Lib/test/regrtest.py -uall -rwW
 
 .. note::
    Running ``Lib/test/regrtest.py`` is exactly equivalent to running
diff -r 3b30c415c9a5 committing.rst
--- a/committing.rst	Sun Mar 31 19:46:14 2013 +0200
+++ b/committing.rst	Sun Apr 07 15:13:20 2013 +0300
@@ -19,7 +19,7 @@
 Patch Checklist
 ---------------
 
-Here's the simple patch checklist that ``make patchcheck`` (or ``./python.exe
+Here's the simple patch checklist that ``make patchcheck`` (or ``python.exe
 Tools/scripts/patchcheck.py`` on Windows) will run through
 on a system that uses the makefile to build Python:
 
diff -r 3b30c415c9a5 patch.rst
--- a/patch.rst	Sun Mar 31 19:46:14 2013 +0200
+++ b/patch.rst	Sun Apr 07 15:13:20 2013 +0300
@@ -100,7 +100,7 @@
 that not all checks apply to non-core developers).  On Windows, use this
 command::
 
-   ./python.exe Tools/scripts/patchcheck.py
+   python.exe Tools/scripts/patchcheck.py
 
 Assuming you are using the :ref:`basic approach <workflow>` suggested earlier,
 just type the following::
diff -r 3b30c415c9a5 setup.rst
--- a/setup.rst	Sun Mar 31 19:46:14 2013 +0200
+++ b/setup.rst	Sun Apr 07 15:13:20 2013 +0300
@@ -157,7 +157,7 @@
 
 Once CPython is done building you will then have a working build
 that can be run in-place; ``./python`` on most machines (and what is used in
-all examples), ``./python.exe`` wherever a case-insensitive filesystem is used
+all examples), ``python.exe`` wherever a case-insensitive filesystem is used
 (e.g. on OS X by default), in order to avoid conflicts with the ``Python``
 directory. There is normally no need to install your built copy
 of Python! The interpreter will realize where it is being run from