From 85e8c810a29cca8faea6cbd93169cf7051cd65b5 Mon Sep 17 00:00:00 2001 From: Steve Dougherty Date: Tue, 17 May 2016 00:26:02 +0200 Subject: [PATCH] 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 | 2 +- find/util.c | 2 +- xargs/xargs.1 | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/find.texi b/doc/find.texi index 93c67c3b..b3c5d106 100644 --- a/doc/find.texi +++ b/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 diff --git a/find/util.c b/find/util.c index f35924c7..0e795719 100644 --- a/find/util.c +++ b/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); diff --git a/xargs/xargs.1 b/xargs/xargs.1 index b0555296..68377868 100644 --- a/xargs/xargs.1 +++ b/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