Spelling fixes: developpers -> developers; curiosly -> curiously

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12798

diff --git a/NEWS b/NEWS
index fd52dfd0b970ce7d836d6893fa44722050054034..a98096bda22e0fe631a3a77a43a648979bc46362 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -64,7 +64,7 @@ xxx Don't forget to update VALGRIND_MAJOR/MINOR before release
 * The C++ demangler has been updated so as to work well with C++ 
   compiled by up to at least g++ 4.6.
 
-* Tool developpers can make replacement/wrapping more flexible thanks
+* Tool developers can make replacement/wrapping more flexible thanks
   to the new option --soname-synonyms.
 
 * The new option --fair-sched allows to control the locking mechanism
@@ -72,7 +72,7 @@ xxx Don't forget to update VALGRIND_MAJOR/MINOR before release
   and scheduling of multithreaded applications (in particular
   on multiprocessor/multicore systems).
 
-* For tool developpers: support to run Valgrind on Valgrind has been improved.
+* For tool developers: support to run Valgrind on Valgrind has been improved.
 
 * gdbserver now shows the float shadow registers as integer
   rather than float values, as the shadow values are mostly
@@ -3415,7 +3415,7 @@ Three months worth of bug fixes, roughly.  Most significant single
 change is improved SSE/SSE2 support, mostly thanks to Dirk Mueller.
 
 20031012 builds on Red Hat Fedora ("Severn") but doesn't really work
-(curiosly, mozilla runs OK, but a modest "ls -l" bombs).  I hope to
+(curiously, mozilla runs OK, but a modest "ls -l" bombs).  I hope to
 get a working version out soon.  It may or may not work ok on the
 forthcoming SuSE 9; I hear positive noises about it but haven't been
 able to verify this myself (not until I get hold of a copy of 9).

diff --git a/gdbserver_tests/README_DEVELOPERS b/gdbserver_tests/README_DEVELOPERS
index e33eb033876c2423fba9b3ed0068143d41f507cc..2f953b2d8718c2931643040aa187b585f737619d 100644 (file)
--- a/gdbserver_tests/README_DEVELOPERS
+++ b/gdbserver_tests/README_DEVELOPERS
@@ -102,7 +102,7 @@ Two approaches have been looked at:
   V: use the 'vg_regtest' approach used by the rest of Valgrind tests
   G: use the gdb Dejagnu test framework.
 
-Advantages of V: much simpler that G, known by Valgrind developpers,
+Advantages of V: much simpler that G, known by Valgrind developers,
 no additional dependency for the Valgrind build and test.
 
 Disadvantages of V: not well suited to testing of interactive tools,