doc: fix spelling of "output"

* doc/find.texi (node Controlling Parallelism): s/ouptut/output/
* xargs/xargs.1: Likewise.
* find/util.c (cleanup): While at it, fix the same typo here
in a comment, too.

Copyright-paperwork-exempt: Yes

doc/find.texi

@@ -2589,7 +2589,7 @@ overall latency by overlapping their waiting time.
 
 If you are running commands in parallel, you need to think about how
 they should arbitrate access to any resources that they share.  For
-example, if more than one of them tries to print to stdout, the ouptut
+example, if more than one of them tries to print to stdout, the output
 will be produced in an indeterminate order (and very likely mixed up)
 unless the processes collaborate in some way to prevent this.  Using
 some kind of locking scheme is one way to prevent such problems.  In

find/util.c

@@ -575,7 +575,7 @@ cleanup (void)
       complete_pending_execdirs ();
     }
 
-  /* Close ouptut files and NULL out references to them. */
+  /* Close output files and NULL out references to them. */
   sharefile_destroy (state.shared_files);
   if (eval_tree)
     traverse_tree (eval_tree, undangle_file_pointers);

xargs/xargs.1

@@ -242,7 +242,7 @@ another.
 .B Please note
 that it is up to the called processes to properly manage parallel
 access to shared resources.  For example, if more than one of them
-tries to print to stdout, the ouptut will be produced in an
+tries to print to stdout, the output will be produced in an
 indeterminate order (and very likely mixed up) unless the processes
 collaborate in some way to prevent this.  Using some kind of locking
 scheme is one way to prevent such problems.  In general, using a