From 0ddff13b5626077e81335982068a064ba7fb108e Mon Sep 17 00:00:00 2001
From: Mirek Jahoda <mjahoda@redhat.com>
Date: Oct 23 2017 15:36:22 +0000
Subject: Update Tasks-Descriptors.xml - typos fixed


---

diff --git a/en-US/Tasks-Descriptors.xml b/en-US/Tasks-Descriptors.xml
index 1d30b97..ca4c884 100644
--- a/en-US/Tasks-Descriptors.xml
+++ b/en-US/Tasks-Descriptors.xml
@@ -24,7 +24,7 @@
       itself, see <xref
       linkend="sect-Defensive_Coding-Tasks-Descriptors-Limit"/>), and
       the kernel resources are not freed.  Therefore, it is important
-      to close all descriptors at the earlierst point in time
+      to close all descriptors at the earliest point in time
       possible, but not earlier.
     </para>
     <section>
@@ -54,7 +54,7 @@
 	descriptors, descriptors are reused very quickly.  Unless
 	descriptor closing and other operations on the same file
 	descriptor are synchronized (typically, using a mutex), there
-	will be race coniditons and I/O operations will be applied to
+	will be race conditons and I/O operations will be applied to
 	the wrong file descriptor.
       </para>
       <para>
@@ -176,7 +176,7 @@
 	  Traditionally, this was implemented as a loop over file
 	  descriptors ranging from <literal>3</literal> to
 	  <literal>255</literal> and later <literal>1023</literal>.
-	  But this is only an approximatio because it is possible to
+	  But this is only an approximation because it is possible to
 	  create file descriptors outside this range easily (see <xref
 	  linkend="sect-Defensive_Coding-Tasks-Descriptors-Limit"/>).
 	  Another approach reads <filename>/proc/self/fd</filename>