From: Daniel Gruno
Date: Tue, 17 Apr 2012 07:19:18 +0000 (+0000)
Subject: conditons -> conditions
X-Git-Tag: 2.5.0-alpha~7147
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=4c3bf430cc419fcb417a0510dd5b74baa4ee9d2d;p=thirdparty%2Fapache%2Fhttpd.git
conditons -> conditions
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1326960 13f79535-47bb-0310-9956-ffa450edef68
---
diff --git a/docs/manual/developer/thread_safety.html.en b/docs/manual/developer/thread_safety.html.en
index 05c1ccbff58..69377694b9c 100644
--- a/docs/manual/developer/thread_safety.html.en
+++ b/docs/manual/developer/thread_safety.html.en
@@ -25,7 +25,7 @@
that every function called from Apache be thread safe. When linking in 3rd
party extensions it can be difficult to determine whether the resulting
server will be thread safe. Casual testing generally won't tell you this
- either as thread safety problems can lead to subtle race conditons that
+ either as thread safety problems can lead to subtle race conditions that
may only show up in certain conditions under heavy load.
Global and static variables
diff --git a/docs/manual/developer/thread_safety.xml b/docs/manual/developer/thread_safety.xml
index 4c92753f9e9..9ba0bace15c 100644
--- a/docs/manual/developer/thread_safety.xml
+++ b/docs/manual/developer/thread_safety.xml
@@ -30,7 +30,7 @@
that every function called from Apache be thread safe. When linking in 3rd
party extensions it can be difficult to determine whether the resulting
server will be thread safe. Casual testing generally won't tell you this
- either as thread safety problems can lead to subtle race conditons that
+ either as thread safety problems can lead to subtle race conditions that
may only show up in certain conditions under heavy load.