GNOME.org
 

[gnome-devel-docs] Changed references of GTK+ to GTK, removed trailing spaces in various .page files.

commit 19ae0b295b59ec4bb773ffc3f8885484bdebf6fb
Author: J Arun Mani <j arunmani protonmail com>
Date:   Fri Apr 17 20:44:42 2020 +0530

    Changed references of GTK+ to GTK, removed trailing spaces in various .page files.

 hig/C/application-basics.page                 |  4 ++--
 hig/C/compatibility.page                      | 10 +++++-----
 hig/C/dialogs.page                            |  8 ++++----
 hig/C/display-compatibility.page              |  4 ++--
 hig/C/drop-down-lists.page                    |  4 ++--
 hig/C/grids.page                              |  4 ++--
 hig/C/icons-and-artwork.page                  |  4 ++--
 hig/C/index.page                              |  4 ++--
 hig/C/keyboard-input.page                     |  8 ++++----
 hig/C/pointer-and-touch-input.page            |  6 +++---
 hig/C/primary-windows.page                    |  4 ++--
 hig/C/search.page                             |  4 ++--
 hig/C/selection-mode.page                     |  4 ++--
 hig/C/writing-style.page                      |  3 +--
 optimization-guide/C/harmful.page             |  2 +-
 optimization-guide/C/introduction.page        |  3 +--
 style-guide/C/index.page                      | 10 +++++-----
 style-guide/C/style-language-conventions.page | 12 ++++++------
 style-guide/C/style-principles.page           | 20 ++++++++++----------
 style-guide/C/style-tone.page                 | 12 ++++++------
 style-guide/C/terms-complete.page             | 10 +++++-----
 style-guide/C/terms-desktop.page              | 12 ++++++------
 style-guide/C/terms-interactions.page         | 14 +++++++-------
 style-guide/C/terms-objects.page              | 12 ++++++------
 style-guide/C/terms-principles.page           | 12 ++++++------
 style-guide/C/terms-widgets.page              | 16 ++++++++--------
 26 files changed, 102 insertions(+), 104 deletions(-)
---
diff --git a/hig/C/application-basics.page b/hig/C/application-basics.page
index 55528eac..0edee8a3 100644
--- a/hig/C/application-basics.page
+++ b/hig/C/application-basics.page
@@ -8,7 +8,7 @@
       <email>aday gnome org</email>
     </credit>
     <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
-    <desc>Basic application characteristics.</desc>    
+    <desc>Basic application characteristics.</desc>
   </info>
 
 <title>Application basics</title>
@@ -60,4 +60,4 @@
 
 <!-- Possible additional section on defining scope. "A successful application does one thing, and does it 
well." -->
 
-</page>
+</page>
\ No newline at end of file
diff --git a/hig/C/compatibility.page b/hig/C/compatibility.page
index dabf994e..5e664bcc 100644
--- a/hig/C/compatibility.page
+++ b/hig/C/compatibility.page
@@ -8,12 +8,12 @@
       <email>aday gnome org</email>
     </credit>
     <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
-    <desc>Using the HIG for cross-platform or GNOME 2 style applications.</desc>   
+    <desc>Using the HIG for cross-platform or GNOME 2 style applications.</desc>
   </info>
 
 <title>Compatibility</title>
 
-<p>These Human Interface Guidelines are primarily targeted towards new GTK+ and GNOME applications, with an 
emphasis on GNOME 3 integration. However, they are also intended to be useful to cross-platform applications, 
as well as older applications, which may have been designed and implemented in accordance with the GNOME 2 
HIG.</p>
+<p>These Human Interface Guidelines are primarily targeted towards new GTK and GNOME applications, with an 
emphasis on GNOME 3 integration. However, they are also intended to be useful to cross-platform applications, 
as well as older applications, which may have been designed and implemented in accordance with the GNOME 2 
HIG.</p>
 
 <section id="cross-platform-compatibility">
 <title>Cross-platform compatibility</title>
@@ -35,14 +35,14 @@
 
 <list>
 <item><p>Utilizing new user interface elements, such as popovers.</p></item>
-<item><p>Guidance on new GTK+ abilities, like animations.</p></item>
+<item><p>Guidance on new GTK abilities, like animations.</p></item>
 <item><p>Modernized guidance on subjects such as visual layout, typography and icon usage.</p></item>
 </list>
 
-<p>Incorporating these elements of the guidelines can enhance your application without requiring a major 
redesign, and all GTK+ and GNOME applications can benefit from them.</p>
+<p>Incorporating these elements of the guidelines can enhance your application without requiring a major 
redesign, and all GTK and GNOME applications can benefit from them.</p>
 
 <p>These Human Interface Guidelines have been designed to assist you in determining the best design for your 
application, rather than proposing a single template to be used in all applications. As such, while they 
recommend <link xref="header-bars">header bars</link> over <link xref="menu-bars">menu bars</link>, they 
provide guidance on both approaches.</p>
 
 </section>
 
-</page>
+</page>
\ No newline at end of file
diff --git a/hig/C/dialogs.page b/hig/C/dialogs.page
index 609beab7..69bcc446 100644
--- a/hig/C/dialogs.page
+++ b/hig/C/dialogs.page
@@ -4,7 +4,7 @@
 
   <info>
     <link type="guide" xref="patterns#primary"/>
-    <desc>Secondary windows that appear over primary, parent windows</desc>  
+    <desc>Secondary windows that appear over primary, parent windows</desc>
     <credit type="author">
       <name>Allan Day</name>
       <email>aday gnome org</email>
@@ -28,7 +28,7 @@
 
 <p>Dialogs are secondary windows that appear over a primary, parent window. They are used to present 
additional information or controls, including preferences and properties, or to present messages or 
questions.</p>
 
-<p>GTK+ provides a number of stock dialogs that can be used, such as for printing or color selection.</p>
+<p>GTK provides a number of stock dialogs that can be used, such as for printing or color selection.</p>
 
 <p>There are three basic types of dialogs.</p>
 
@@ -82,7 +82,7 @@
 <section id="action-dialog-examples">
 <title>Examples</title>
 
-<p>Many of the stock GTK+ dialogs are action dialogs. The print dialog is a good example: it is displayed in 
response to the user using the print action, and presents information and options for that print action. The 
two header bar buttons allow the print action to either be cancelled or carried out.</p>
+<p>Many of the stock GTK dialogs are action dialogs. The print dialog is a good example: it is displayed in 
response to the user using the print action, and presents information and options for that print action. The 
two header bar buttons allow the print action to either be cancelled or carried out.</p>
 
 </section>
 </section>
@@ -174,4 +174,4 @@
 </list>
 </section>
 
-</page>
+</page>
\ No newline at end of file
diff --git a/hig/C/display-compatibility.page b/hig/C/display-compatibility.page
index 97517b6f..1be15dad 100644
--- a/hig/C/display-compatibility.page
+++ b/hig/C/display-compatibility.page
@@ -8,7 +8,7 @@
       <email>aday gnome org</email>
     </credit>
     <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
-    <desc></desc>  
+    <desc></desc>
   </info>
 
 <title>Display compatibility</title>
@@ -37,4 +37,4 @@
 <p>Since half-screen snap is only useful when windows are used in parallel, applications that are used in 
isolation do not need to support half-screen snap (a music player is a good example of this).</p>
 
 </section>
-</page>
+</page>
\ No newline at end of file
diff --git a/hig/C/drop-down-lists.page b/hig/C/drop-down-lists.page
index 56c7830e..b71968ba 100644
--- a/hig/C/drop-down-lists.page
+++ b/hig/C/drop-down-lists.page
@@ -34,7 +34,7 @@
 <title>General guidelines</title>
 
 <list>
-<item><p>While GTK+ does provide a specific combobox widget, it is recommended that drop-down lists are 
constructed using a combination of a button and a popover. This allows more comfortable scrolling for long 
lists, and allows search to be integrated into the list. Using this approach also allows the current selected 
item to always be displayed.</p></item>
+<item><p>While GTK does provide a specific combobox widget, it is recommended that drop-down lists are 
constructed using a combination of a button and a popover. This allows more comfortable scrolling for long 
lists, and allows search to be integrated into the list. Using this approach also allows the current selected 
item to always be displayed.</p></item>
 <item><p>If the number of items is very large, provide a search function that filters the list.</p></item>
 <item><p>Label the drop-down list button with a text label above it or to its left, using <link 
xref="writing-style#capitalization">sentence capitalization</link>. Provide an access key in the label that 
allows the user to give focus directly to the drop-down list.</p></item>
 <item><p>Use <link xref="writing-style#capitalization">sentence capitalization</link> for drop-down list 
items, for example <gui>Switched movement</gui>.</p></item>
@@ -59,4 +59,4 @@
 
 </section>
 
-</page>
+</page>
\ No newline at end of file
diff --git a/hig/C/grids.page b/hig/C/grids.page
index 906132da..21a4e958 100644
--- a/hig/C/grids.page
+++ b/hig/C/grids.page
@@ -4,7 +4,7 @@
       id="grids">
 
   <info>
-    <link type="guide" xref="patterns#primary"/>   
+    <link type="guide" xref="patterns#primary"/>
     <desc>Grids of thumbnails or icons</desc>
     <credit type="author">
       <name>Allan Day</name>
@@ -48,4 +48,4 @@
 </list>
 </section>
 
-</page>
+</page>
\ No newline at end of file
diff --git a/hig/C/icons-and-artwork.page b/hig/C/icons-and-artwork.page
index 166b7496..613e881a 100644
--- a/hig/C/icons-and-artwork.page
+++ b/hig/C/icons-and-artwork.page
@@ -11,7 +11,7 @@
       <name>Jakub Steiner</name>
     </credit>
     <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
-    <desc>Selecting and creating icons.</desc>   
+    <desc>Selecting and creating icons.</desc>
   </info>
 
 <title>Icons and artwork</title>
@@ -70,4 +70,4 @@
 
 </section>
 
-</page>
+</page>
\ No newline at end of file
diff --git a/hig/C/index.page b/hig/C/index.page
index 6f83252f..7c5ba215 100644
--- a/hig/C/index.page
+++ b/hig/C/index.page
@@ -14,7 +14,7 @@
 <title>GNOME Human Interface Guidelines</title>
 <media type="image" its:translate="no" src="figures/hig.png"/>
 
-<p>Whether you are a developer or a designer, these guidelines contain everything you need to design 
effective applications using GTK+. They cover design principles for GNOME 3, common guidelines such as how to 
write text and use images and icons, as well as a library of design patterns which you can use in your 
application.</p>
+<p>Whether you are a developer or a designer, these guidelines contain everything you need to design 
effective applications using GTK. They cover design principles for GNOME 3, common guidelines such as how to 
write text and use images and icons, as well as a library of design patterns which you can use in your 
application.</p>
 
 <p>While the HIG places an emphasis on designing for GNOME 3, it can also be used to create cross-platform 
applications, as well as for applications that have previously followed the GNOME 2 Human Interface 
Guidelines. The <link xref="compatibility">compatibility guidelines</link> contain more information on 
this.</p>
 
@@ -86,4 +86,4 @@
 
 </section>
 
-</page>
+</page>
\ No newline at end of file
diff --git a/hig/C/keyboard-input.page b/hig/C/keyboard-input.page
index 62ce2b97..8adc3031 100644
--- a/hig/C/keyboard-input.page
+++ b/hig/C/keyboard-input.page
@@ -21,7 +21,7 @@
       <name>Colin Robertson</name>
     </credit>
     <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
-    <desc>Keyboard navigation, access and shortcut keys.</desc>  
+    <desc>Keyboard navigation, access and shortcut keys.</desc>
   </info>
 
 <title>Keyboard input</title>
@@ -30,7 +30,7 @@
 
 <p>You should ensure that all the functionality provided by your application can be accessed using a 
keyboard. Trying to use your application with only a keyboard is a great way to test this.</p>
 
-<p>Keyboard interaction has three aspects in GNOME and GTK+: navigation, access keys, and shortcut keys. 
<link xref="search">Search</link> is another, additional aspect.</p>
+<p>Keyboard interaction has three aspects in GNOME and GTK: navigation, access keys, and shortcut keys. 
<link xref="search">Search</link> is another, additional aspect.</p>
 
 <section id="keyboard-navigation">
 <title>Keyboard navigation</title>
@@ -38,7 +38,7 @@
 <p>Make sure that it is possible to move around and interact with every part of your user interface using 
the keyboard, by following these guidelines.</p>
 
 <list>
-<item><p>Follow the standard GNOME keys for navigation. <key>Tab</key> is the standard key for moving around 
an interface with GTK+ and GNOME.</p></item>
+<item><p>Follow the standard GNOME keys for navigation. <key>Tab</key> is the standard key for moving around 
an interface with GTK and GNOME.</p></item>
 <item><p>Use a logical keyboard navigation order. When navigating around a window with <key>Tab</key>, 
keyboard focus should move between controls in a predictable order. In Western locales, this is normally left 
to right and top to bottom.</p></item>
 <item><p>In addition to navigation using <key>Tab</key>, make an effort to allow movement using the arrow 
keys, both within user interface elements (such as lists, icon grids or sidebars), and between 
them.</p></item>
 </list>
@@ -743,4 +743,4 @@
 </section>
 </section>
 
-</page>
+</page>
\ No newline at end of file
diff --git a/hig/C/pointer-and-touch-input.page b/hig/C/pointer-and-touch-input.page
index 32c1a14b..b531d8f6 100644
--- a/hig/C/pointer-and-touch-input.page
+++ b/hig/C/pointer-and-touch-input.page
@@ -11,7 +11,7 @@
       <name>Jakub Steiner</name>
     </credit>
     <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
-    <desc>Mouse, touchpad and touchscreen interaction.</desc>  
+    <desc>Mouse, touchpad and touchscreen interaction.</desc>
   </info>
 
 <title>Pointer and touch input</title>
@@ -105,7 +105,7 @@
 <section id="touch-input">
 <title>Touch input</title>
 
-<p>Touch screens are also an increasingly common part of modern computer hardware, and applications created 
with GTK+ are likely to be used with hardware that incorporates a touch screen. To make the most of this 
hardware, and to conform to users’ expectations, it is therefore important to consider touch input as a part 
of application design.</p>
+<p>Touch screens are also an increasingly common part of modern computer hardware, and applications created 
with GTK are likely to be used with hardware that incorporates a touch screen. To make the most of this 
hardware, and to conform to users’ expectations, it is therefore important to consider touch input as a part 
of application design.</p>
 
 <section id="application-touch-conventions">
 <title>Application touch conventions</title>
@@ -218,4 +218,4 @@
 
 </section>
 </section>
-</page>
+</page>
\ No newline at end of file
diff --git a/hig/C/primary-windows.page b/hig/C/primary-windows.page
index 11ebd9ff..e5498d5b 100644
--- a/hig/C/primary-windows.page
+++ b/hig/C/primary-windows.page
@@ -4,7 +4,7 @@
 
   <info>
     <link type="guide" xref="patterns#primary"/>
-    <desc>The main window(s) for your application</desc> 
+    <desc>The main window(s) for your application</desc>
     <credit type="author">
       <name>Allan Day</name>
       <email>aday gnome org</email>
@@ -91,4 +91,4 @@
 
 </section>
 
-</page>
+</page>
\ No newline at end of file
diff --git a/hig/C/search.page b/hig/C/search.page
index d6dcda03..d8c31389 100644
--- a/hig/C/search.page
+++ b/hig/C/search.page
@@ -4,7 +4,7 @@
 
   <info>
     <link type="guide" xref="patterns#primary"/>
-    <desc>Find and filter content by typing</desc> 
+    <desc>Find and filter content by typing</desc>
     <credit type="author">
       <name>Allan Day</name>
       <email>aday gnome org</email>
@@ -75,4 +75,4 @@ In primary windows, the search bar is typically hidden until it is activated by
 </list>
 </section>
 
-</page>
+</page>
\ No newline at end of file
diff --git a/hig/C/selection-mode.page b/hig/C/selection-mode.page
index a9e925c5..63841ded 100644
--- a/hig/C/selection-mode.page
+++ b/hig/C/selection-mode.page
@@ -4,7 +4,7 @@
 
   <info>
     <link type="guide" xref="patterns#primary"/>
-    <desc>Pattern for selecting content items</desc>  
+    <desc>Pattern for selecting content items</desc>
     <credit type="author">
       <name>Allan Day</name>
       <email>aday gnome org</email>
@@ -52,4 +52,4 @@
 </list>
 
 </section>
-</page>
+</page>
\ No newline at end of file
diff --git a/hig/C/writing-style.page b/hig/C/writing-style.page
index 232c9413..a269f6f8 100644
--- a/hig/C/writing-style.page
+++ b/hig/C/writing-style.page
@@ -30,7 +30,7 @@
 
     <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
 
-    <desc>Writing text for your user interface, including capitalization rules.</desc>    
+    <desc>Writing text for your user interface, including capitalization rules.</desc>
 
   </info>
 
@@ -113,4 +113,3 @@
 
 </page>
 
-
diff --git a/optimization-guide/C/harmful.page b/optimization-guide/C/harmful.page
index c6942c39..e5e8240c 100644
--- a/optimization-guide/C/harmful.page
+++ b/optimization-guide/C/harmful.page
@@ -68,4 +68,4 @@
     <p>
         The trouble with disk seeks are compounded for reads, which is unfortunately what we are doing.  
Remember, reads are generally synchronous while writes are asynchronous.  This only compounds the problem, 
serializing each read, and contributing to program latency.
     </p>
-</page>        
+</page>
\ No newline at end of file
diff --git a/optimization-guide/C/introduction.page b/optimization-guide/C/introduction.page
index ffaef2e1..ae6dde08 100644
--- a/optimization-guide/C/introduction.page
+++ b/optimization-guide/C/introduction.page
@@ -14,7 +14,7 @@
             Traditional optimization tackles concepts like CPU use, code size, the number of mouse clicks 
and the memory use of the program. This second list has been chosen to correlate with the first list, however 
there is an important difference: The person using GNOME doesn't care about the second list, but they care a 
lot about the first list. When optimizing GNOME programs we will reduce CPU use, memory use and all those 
things, but these are the means to the end, not the final goal. We are optimizing for people.
         </p>
 
-       <section id="doing-the-optimization">        
+       <section id="doing-the-optimization">
           <title>Doing the Optimization</title>
         <p>
             The previous section omitted one important qualifier: To optimize something it has to be 
measurable. You can't measure happiness. However, you can measure start-up time so you can tell if you have 
improved it. Happiness will then, hopefully, follow.
@@ -172,4 +172,3 @@
   </page>
 
 
-
diff --git a/style-guide/C/index.page b/style-guide/C/index.page
index 87462957..e0ddf406 100644
--- a/style-guide/C/index.page
+++ b/style-guide/C/index.page
@@ -3,16 +3,16 @@
       id="index">
 
   <info>
-  
+
     <desc>Guidelines for writers for the GNOME platform.</desc>
-    
+
     <revision pkgversion="3.0" version="0.1" date="2010-12-23" status="stub"/>
-    
+
     <credit type="author">
       <name>GNOME Documentation Project</name>
       <email>gnome-doc-list gnome org</email>
     </credit>
-    
+
   </info>
 
 <title>Style and Terminology</title>
@@ -26,4 +26,4 @@
  <title>Terminology</title>
 </section>
 
-</page>
+</page>
\ No newline at end of file
diff --git a/style-guide/C/style-language-conventions.page b/style-guide/C/style-language-conventions.page
index c676e642..9b06f6e5 100644
--- a/style-guide/C/style-language-conventions.page
+++ b/style-guide/C/style-language-conventions.page
@@ -3,20 +3,20 @@
       id="style-language-conventions">
 
   <info>
-  
+
     <link type="guide" xref="index#style"/>
-    
+
     <desc>How you should construct sentences.</desc>
-    
+
     <revision pkgversion="3.0" version="0.1" date="2010-12-23" status="stub"/>
-    
+
     <credit type="author">
       <name>GNOME Documentation Project</name>
       <email>gnome-doc-list gnome org</email>
     </credit>
-    
+
   </info>
 
 <title>Language Conventions</title>
 
-</page>
+</page>
\ No newline at end of file
diff --git a/style-guide/C/style-principles.page b/style-guide/C/style-principles.page
index be9eee42..e3dd1dd7 100644
--- a/style-guide/C/style-principles.page
+++ b/style-guide/C/style-principles.page
@@ -3,18 +3,18 @@
       id="style-principles">
 
   <info>
-  
+
     <link type="guide" xref="index#style"/>
-    
+
     <desc>Guiding principles for writing documentation.</desc>
-    
+
     <revision pkgversion="3.0" version="0.1" date="2010-12-23" status="draft"/>
-    
+
     <credit type="author">
       <name>GNOME Documentation Project</name>
       <email>gnome-doc-list gnome org</email>
     </credit>
-    
+
   </info>
 
 <title>Style Principles</title>
@@ -23,22 +23,22 @@
   <cite>Henry David Thoreau</cite>
   <p>Our life is frittered away by detail.... Simplify, simplify.</p>
  </quote>
- 
+
  <quote>
   <cite><em>The Elements of Style</em>, William Strunck Jr. and E. B. White</cite>
   <p>Vigorous writing is concise. A sentence should contain no unnecessary words, a paragraph no unnecessary 
sentences, for the same reason that a drawing should have no unnecessary lines and a machine no unnecessary 
parts. This requires not that the writer make all his sentences short, or that he should avoid all detail and 
treat his subjects only in outline, but that every sentence tell.</p>
  </quote>
- 
+
  <quote>
   <cite>Thomas Mann</cite>
   <p>A writer is someone for whom writing is more difficult than it is for other people.</p>
  </quote>
- 
+
  <quote>
   <cite>John Ruskin</cite>
   <p>Say all you have to say in the fewest possible words, or your reader will be sure to skip them; and in 
the plainest possible words or he will certainly misunderstand them.</p>
  </quote>
- 
+
 <section id="human">
  <title>You are human, and so are your readers</title>
  <p>There is a tendency in technical writing to be formulaic, to rely on using the same structures again and 
again. This makes your writing boring and unsatisfying. Avoid this at all costs - readers won't take the 
information on board as effectively if they are bored, and you won't be getting the satisfaction of 
exercising your creativity.</p>
@@ -78,4 +78,4 @@
  <p>Likewise, absolute technical correctness is vehemently <em>not</em> the aim of our technical writing. 
It's fine to abuse terms if doing so would make your text more understandable for the reader.</p>
 </section>
 
-</page>
+</page>
\ No newline at end of file
diff --git a/style-guide/C/style-tone.page b/style-guide/C/style-tone.page
index 76407811..b09e1bb2 100644
--- a/style-guide/C/style-tone.page
+++ b/style-guide/C/style-tone.page
@@ -3,18 +3,18 @@
       id="style-tone">
 
   <info>
-  
+
     <link type="guide" xref="index#style"/>
-    
+
     <desc>Writing in an appropriate tone will help readers relate to the text.</desc>
-    
+
     <revision pkgversion="3.0" version="0.1" date="2010-12-23" status="draft"/>
-    
+
     <credit type="author">
       <name>GNOME Documentation Project</name>
       <email>gnome-doc-list gnome org</email>
     </credit>
-    
+
   </info>
 
 <title>Tone</title>
@@ -53,4 +53,4 @@
  </quote>
 </section>
 
-</page>
+</page>
\ No newline at end of file
diff --git a/style-guide/C/terms-complete.page b/style-guide/C/terms-complete.page
index 79a05ae4..1a5e3bfe 100644
--- a/style-guide/C/terms-complete.page
+++ b/style-guide/C/terms-complete.page
@@ -5,13 +5,13 @@
       id="terms-complete">
 
 <info>
-  
+
   <link type="guide" xref="index#terms"/>
-    
+
   <desc>A complete list of terminology recommendations.</desc>
-    
+
   <revision pkgversion="3.0" version="0.1" date="2010-12-23" status="stub"/>
-    
+
   <credit type="author">
     <name>GNOME Documentation Project</name>
     <email>gnome-doc-list gnome org</email>
@@ -74,4 +74,4 @@
 
 <title>Complete list of terms</title>
 
-</page>
+</page>
\ No newline at end of file
diff --git a/style-guide/C/terms-desktop.page b/style-guide/C/terms-desktop.page
index 1876ecd6..11c07ce7 100644
--- a/style-guide/C/terms-desktop.page
+++ b/style-guide/C/terms-desktop.page
@@ -3,22 +3,22 @@
       id="terms-desktop">
 
   <info>
-  
+
     <link type="guide" xref="index#terms"/>
-    
+
     <desc>Terms to be used when referring to the major components of the desktop environment.</desc>
-    
+
     <revision pkgversion="3.0" version="0.1" date="2010-12-23" status="stub"/>
-    
+
     <credit type="author">
       <name>GNOME Documentation Project</name>
       <email>gnome-doc-list gnome org</email>
     </credit>
-    
+
   </info>
 
 <title>Desktop components</title>
 
 <p>Workspaces, etc.</p>
 
-</page>
+</page>
\ No newline at end of file
diff --git a/style-guide/C/terms-interactions.page b/style-guide/C/terms-interactions.page
index d0abd259..0968ab16 100644
--- a/style-guide/C/terms-interactions.page
+++ b/style-guide/C/terms-interactions.page
@@ -3,18 +3,18 @@
       id="terms-interactions">
 
   <info>
-  
+
     <link type="guide" xref="index#terms"/>
-    
+
     <desc>How to describe the way the user interacts with the user interface.</desc>
-    
+
     <revision pkgversion="3.0" version="0.1" date="2010-12-23" status="incomplete"/>
-    
+
     <credit type="author">
       <name>GNOME Documentation Project</name>
       <email>gnome-doc-list gnome org</email>
     </credit>
-    
+
   </info>
 
 <title>Interactions</title>
@@ -23,7 +23,7 @@
  <title>Mouse and keyboard actions</title>
  <p>Users should be able to distinguish between actions which they have to perform with the mouse or with 
the keyboard, respectively.</p>
 
- <list> 
+ <list>
   <item><p>To perform this action, click <gui>Apply</gui>.</p></item>
   <item><p>To perform this action, press <key>Enter</key>.</p></item>
  </list>
@@ -37,4 +37,4 @@
  <p>In fact, we cannot <em>press</em> a button. The physical process <em>to press</em> isn't adaptable to a 
virtual object. Instead, we <em>click</em> with the mouse or another pointing device.</p>
 </section>
 
-</page>
+</page>
\ No newline at end of file
diff --git a/style-guide/C/terms-objects.page b/style-guide/C/terms-objects.page
index 3ca64e9c..a5293670 100644
--- a/style-guide/C/terms-objects.page
+++ b/style-guide/C/terms-objects.page
@@ -3,18 +3,18 @@
       id="terms-objects">
 
   <info>
-  
+
     <link type="guide" xref="index#terms"/>
-    
+
     <desc>Terms for describing objects that the user encounters in the user interface, such as files and 
folders.</desc>
-    
+
     <revision pkgversion="3.0" version="0.1" date="2010-12-23" status="stub"/>
-    
+
     <credit type="author">
       <name>GNOME Documentation Project</name>
       <email>gnome-doc-list gnome org</email>
     </credit>
-    
+
   </info>
 
 <title>Objects in the UI</title>
@@ -32,4 +32,4 @@
 </terms>
 
 
-</page>
+</page>
\ No newline at end of file
diff --git a/style-guide/C/terms-principles.page b/style-guide/C/terms-principles.page
index 1f9d7119..32ed17b1 100644
--- a/style-guide/C/terms-principles.page
+++ b/style-guide/C/terms-principles.page
@@ -3,18 +3,18 @@
       id="terms-principles">
 
   <info>
-  
+
     <link type="guide" xref="index#terms"/>
-    
+
     <desc>Some guiding principles to help you decide which terminology to use.</desc>
-    
+
     <revision pkgversion="3.0" version="0.1" date="2010-12-23" status="draft"/>
-    
+
     <credit type="author">
       <name>GNOME Documentation Project</name>
       <email>gnome-doc-list gnome org</email>
     </credit>
-    
+
   </info>
 
 <title>Choosing terminology</title>
@@ -51,4 +51,4 @@
  <p>When deciding on what terminology to use, you should test it on real end-users. This will help to ensure 
that your choices are relevant, understandable and sensible.</p>
 </note>
 
-</page>
+</page>
\ No newline at end of file
diff --git a/style-guide/C/terms-widgets.page b/style-guide/C/terms-widgets.page
index 3cb7ae07..b8cf6b26 100644
--- a/style-guide/C/terms-widgets.page
+++ b/style-guide/C/terms-widgets.page
@@ -3,18 +3,18 @@
       id="terms-widgets">
 
   <info>
-  
+
     <link type="guide" xref="index#terms"/>
-    
+
     <desc>The terms to use when referring to a widget in the user interface.</desc>
-    
+
     <revision pkgversion="3.0" version="0.1" date="2010-12-23" status="stub"/>
-    
+
     <credit type="author">
       <name>GNOME Documentation Project</name>
       <email>gnome-doc-list gnome org</email>
     </credit>
-    
+
   </info>
 
 <title>Widgets</title>
@@ -28,7 +28,7 @@
   </media>
   <p></p>
  </item>
- 
+
  <item>
   <title>List</title>
   <media type="image" mime="image/png" src="media/list.png">
@@ -36,7 +36,7 @@
   </media>
   <p></p>
  </item>
- 
+
  <item>
   <title>Checkbox</title>
   <media type="image" mime="image/png" src="media/checkbox.png">
@@ -47,4 +47,4 @@
 
 </terms>
 
-</page>
+</page>
\ No newline at end of file
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]