[gnome-devel-docs] Fixed bug #614315

[Daniel Mustieles GarcÃa <dmustieles src gnome org>]

commit 3043b67146db5f9a96de64647a45141cdea3ed01
Author: Daniel Mustieles <daniel mustieles gmail com>
Date:   Mon Mar 19 22:34:14 2012 +0100

    Fixed bug #614315

 hig/C/hig-ch-windows.xml |   10 +++++-----
 1 files changed, 5 insertions(+), 5 deletions(-)
---
diff --git a/hig/C/hig-ch-windows.xml b/hig/C/hig-ch-windows.xml
index 2420787..3723733 100644
--- a/hig/C/hig-ch-windows.xml
+++ b/hig/C/hig-ch-windows.xml
@@ -236,7 +236,7 @@ system appear slow, not doing this can cause the window manager to think the app
 
       <para>The most important element of a document-based application's 
 	      window title is the name of the open document.  For other
-	      applications, it usually the name of the application.
+	      applications, it is usually the name of the application.
       </para>
 
       <itemizedlist><title>Guidelines</title>
@@ -517,7 +517,7 @@ system appear slow, not doing this can cause the window manager to think the app
         </listitem>
       </itemizedlist>
 
-      <para>If either these conditions affect only a few of the controls in
+      <para>If either of these conditions affect only a few of the controls in
       your window, arrange those controls together into one or more groups,
       each with its own <guibutton>Apply</guibutton> button. Leave the rest of
       the controls as instant apply.</para>
@@ -1117,7 +1117,7 @@ system appear slow, not doing this can cause the window manager to think the app
         fits best with the button&apos;s role in initiating actions, as
         contrasted with a more passive phrase. For example
         <guibutton>Find</guibutton> and <guibutton>Log In</guibutton> are
-        better buttons than than <guibutton>Yes</guibutton> and
+        better buttons than <guibutton>Yes</guibutton> and
         <guibutton>OK</guibutton>.</para>
       </formalpara>
 
@@ -1138,7 +1138,7 @@ system appear slow, not doing this can cause the window manager to think the app
           <formalpara>
             <title>Cancel Button</title>
 
-            <para>If the alert was produced in response to a user action,
+            <para>If the alert was produced in response to a user's action,
             place a <guibutton>Cancel</guibutton> button immediately to the
             left of the affirmative button. This provides an escape route for
             users to stop an action in response to new information, or just if
@@ -1846,7 +1846,7 @@ saved, in case an error occurs.  Then hide the document window immediately after
         package, add entries for the firewall to /etc/xinetd.conf, restart the
         internet super-daemon, and configure the user&apos;s web browser to
         operate through the firewall. It may be desirable that the user is
-        exposed the series of actions involved in setting up the firewall to
+        exposed to the series of actions involved in setting up the firewall to
         increase the chances that they will be sucessful in making
         modifications later, if they so desire.</para>
       </example>