some wording fixups.

Fri Mar 24 15:22:04 2006  Tim Janik  <timj@imendio.com>

        * glib/tmpl/atomic_operations.sgml: some wording fixups.

diff --git a/docs/reference/ChangeLog b/docs/reference/ChangeLog
index 0e59ccc4c61789c9eb6bef4b3fdd33e30eecf198..0583fa41d28102ce96b5308faf37ed5184f92c29 100644 (file)
--- a/docs/reference/ChangeLog
+++ b/docs/reference/ChangeLog
@@ -1,3 +1,7 @@
+Fri Mar 24 15:22:04 2006  Tim Janik  <timj@imendio.com>
+
+       * glib/tmpl/atomic_operations.sgml: some wording fixups.
+
 2006-03-20  Matthias Clasen  <mclasen@redhat.com>
 
        * glib/tmpl/types.sgml: Document G_HAVE_GINT64 as deprecated.

diff --git a/docs/reference/glib/tmpl/atomic_operations.sgml b/docs/reference/glib/tmpl/atomic_operations.sgml
index 231fc73e092058e6b7d344078ac013bc650fa448..ad3e04b6fd184d2d1107935e7a2d4726647f6b46 100644 (file)
--- a/docs/reference/glib/tmpl/atomic_operations.sgml
+++ b/docs/reference/glib/tmpl/atomic_operations.sgml
@@ -22,9 +22,11 @@ counting a very fast operation.
 <note>
 <para>
 You must not directly read integers or pointers concurrently accessed
-by other threads with with the following functions directly. Always use
-g_atomic_int_get() and g_atomic_pointer_get() respectively. They are
-acting as a memory barrier.
+by multiple threads, but use the atomic accessor functions instead.
+That is, always use g_atomic_int_get() and g_atomic_pointer_get() for
+read outs.
+They provide the neccessary synchonization mechanisms like memory
+barriers to access memory locations concurrently.
 </para> 
 </note>