# HG changeset patch
# User Sergey Budnevitch <sb@waeme.net>
# Date 1350392123 0
# Node ID 7f8e85a508458ce0b23246273983c045406a841e
# Parent  cea4732f68439b69e4018fe46f124a97471f791c
Renamed OX X to Mac OS X for uniformity.

diff -r cea4732f6843 -r 7f8e85a50845 xml/en/docs/nginx_dtrace_pid_provider.xml
--- a/xml/en/docs/nginx_dtrace_pid_provider.xml	Tue Oct 16 12:44:45 2012 +0000
+++ b/xml/en/docs/nginx_dtrace_pid_provider.xml	Tue Oct 16 12:55:23 2012 +0000
@@ -9,7 +9,7 @@
 <article name="Debugging nginx with DTrace pid provider"
 	link="/en/docs/nginx_dtrace_pid_provider.html"
 	lang="en"
-	rev="1"
+	rev="2"
 	toc="no">
 
 <section>
@@ -24,7 +24,7 @@
 option already provides a lot of information about request processing,
 it is sometimes desirable to trace particular parts of code path more
 thoroughly and at the same time omit the rest of debugging output.
-DTrace pid provider (available on Solaris, OS X) is a useful tool to
+DTrace pid provider (available on Solaris, Mac OS X) is a useful tool to
 explore userland program’s internals, since it doesn’t require any code
 changes and it can help with the task.
 A simple DTrace script to trace and print nginx function calls