Fix spelling s/doens't/doesn't/
authorMathieu Parent <math.parent@gmail.com>
Fri, 4 May 2018 20:19:08 +0000 (22:19 +0200)
committerAndrew Bartlett <abartlet@samba.org>
Sat, 12 May 2018 00:09:26 +0000 (02:09 +0200)
Signed-off-by: Mathieu Parent <math.parent@gmail.com>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
Reviewed-by: Garming Sam <garming@catalyst.net.nz>
source4/auth/kerberos/kerberos-notes.txt
source4/auth/kerberos/kerberos-porting-to-mit-notes.txt
source4/torture/basic/delaywrite.c

index 1981328bcf695b5c6a924606854a2e4a42d60b25..69541290ef7c5f5dcdb10e0feb13fa894dc9de40 100644 (file)
@@ -460,7 +460,7 @@ in libkrb5 would be difficult, but valuable.
 
 In the short-term, we deal with blocking by taking over the network
 send() and recv() functions, therefore making them 'semi-async'.  This
-doens't apply to DNS yet.These thread-safety context-variables will
+doesn't apply to DNS yet.These thread-safety context-variables will
 probably present porting problems, during the MIT port.  This will
 probably be most of the work in the port to MIT.
 
index 329558e9f7af5136bb567ac48de9bc6f74ba1ee5..9b478bbd1c1973d2e357d1702679cf4e670557d8 100644 (file)
@@ -383,7 +383,7 @@ when using Kerberos and GSSAPI libraries
       in libkrb5 would be difficult, but valuable.
     * In the short-term, we deal with blocking by taking over the network
       send() and recv() functions, therefore making them 'semi-async'.  This
-      doens't apply to DNS yet.These thread-safety context-variables will
+      doesn't apply to DNS yet.These thread-safety context-variables will
       probably present porting problems, during the MIT port.  This will
       probably be most of the work in the port to MIT.
       This may require more thorough thread-safe-ing work on the MIT libraries.
index 160674f19a149353c9413dac947b471391bc7e02..347871688729e03006f2b9a9652899d8556d255d 100644 (file)
@@ -2924,7 +2924,7 @@ static bool test_delayed_write_update7(struct torture_context *tctx, struct smbc
 
        if (finfo2.basic_info.out.write_time != finfo3.basic_info.out.write_time) {
                torture_result(tctx, TORTURE_FAIL, 
-                       "qpathinfo time doens't match fileinfo time");
+                       "qpathinfo time doesn't match fileinfo time");
                ret = false;
        }