Sched + Tests + Misc typos

sched/sched_customize.cpp

@@ -93,7 +93,7 @@ using std::string;
 
 PLAN_CLASS_SPECS plan_class_specs;
 
-/* is there a plan class spec that restricts the worunit (or batch) */
+/* is there a plan class spec that restricts the workunit (or batch) */
 bool wu_restricted_plan_class;
 
 GPU_REQUIREMENTS gpu_requirements[NPROC_TYPES];
@@ -712,7 +712,7 @@ static inline bool app_plan_opencl(
 ) {
     // opencl_*_<ver> plan classes check for a trailing integer which is
     // used as the opencl version number.  This is compatible with the old
-    // opencl_nvidia_101 and opencl_ati_101 plan classes, but doens't require
+    // opencl_nvidia_101 and opencl_ati_101 plan classes, but doesn't require
     // modifications if someone wants a opencl_nvidia_102 plan class.
     const char *p=plan_class+strlen(plan_class);
     while (isnum(p[-1])) {

sched/sched_locality.cpp

@@ -1391,4 +1391,4 @@ void send_file_deletes() {
 // (7) there are no feasible results for the host, we are finished:
 // (7) exit.
 
-// (8) If addtional results are needed, return to step 4 above.
+// (8) If additional results are needed, return to step 4 above.

sched/sched_types.cpp

@@ -595,7 +595,7 @@ int SCHEDULER_REQUEST::write(FILE* fout) {
 
     fprintf(fout,
         "<scheduler_request>\n"
-        "  <authenticator>%s</authentiicator>\n"
+        "  <authenticator>%s</authenticator>\n"
         "  <platform_name>%s</platform_name>\n"
         "  <cross_project_id>%s</cross_project_id>\n"
         "  <hostid>%lu</hostid>\n"

sched/target_batch.cpp

@@ -9,7 +9,7 @@
 
      The project dir must be defined in the projects config.xml file.
 
-     Input parameter of the form 'batch=[id]' can be passed via url or commmand line.
+     Input parameter of the form 'batch=[id]' can be passed via url or command line.
 
      Example usage from command line:
      ./target_batch batch=1
@@ -42,7 +42,7 @@ Create a batch of low-priority tasks:
 Target batch to dedicated workers:
 /bin/target_batch batch=0
 
-Start dedicated work with USER_ID corresonding to DEDICATED_USER_ID.
+Start dedicated work with USER_ID corresponding to DEDICATED_USER_ID.
 
 Check that these tasks are only assigned to dedicated workers.
 

tests/old/concat_correct_output

@@ -529,7 +529,7 @@
       <li>
               <code>unparsed-entity-uri()</code>.</li>
       </ul>
-          <p CLASS="">As for the fuctions that <i>are</i> implemented, the
+          <p CLASS="">As for the functions that <i>are</i> implemented, the
       following is a list of differences from the spec:
       </p>
           <ul>

tests/old/input

@@ -529,7 +529,7 @@
       <li>
               <code>unparsed-entity-uri()</code>.</li>
       </ul>
-          <p CLASS="">As for the fuctions that <i>are</i> implemented, the
+          <p CLASS="">As for the functions that <i>are</i> implemented, the
       following is a list of differences from the spec:
       </p>
           <ul>

tests/old/test.inc

@@ -32,7 +32,7 @@ assert_options(ASSERT_CALLBACK, 'my_assert_handler');
 
 $errors = 0;
 
-// get an enviroment variable, and abort script if missing
+// get an environment variable, and abort script if missing
 //
 function get_env_var($name, $defvalue = -1) {
     $x = getenv($name);

tests/old/test_sched_moved.py

@@ -2,7 +2,7 @@
 
 ## $Id$
 
-# DOESN"T WORK YET
+# DOESN'T WORK YET
 
 from test_uc import *
 

todo

@@ -167,7 +167,7 @@ CPU benchmarking
     what to do when tests show hardware problem?
     How should we weight factors for credit?
     run CPU tests unobtrusively, periodically
-    check that on/conn/active fracs are maintainted correctly
+    check that on/conn/active fracs are maintained correctly
     check that bandwidth is measured correctly
     measure disk/mem size on all platforms
     get timezone to work

tools/update_versions

@@ -221,7 +221,7 @@ function confirm_sig_gen($name) {
     NOTICE: You have not provided a signature file for $name,
     and your project's code-signing private key is on your server.
 
-    IF YOUR PROJECT IS PUBLICLY ACCESSABLE, THIS IS A SECURITY VULNERABILITY.
+    IF YOUR PROJECT IS PUBLICLY ACCESSIBLE, THIS IS A SECURITY VULNERABILITY.
     PLEASE STOP YOUR PROJECT IMMEDIATELY AND READ:
     https://boinc.berkeley.edu/trac/wiki/CodeSigning