[gnome-devel-docs] hig3: fix broken links



commit d0231ea31169483ccfffc6ebfbfe55f00c1c4bbe
Author: David King <amigadave amigadave com>
Date:   Fri Aug 15 19:41:19 2014 +0100

    hig3: fix broken links

 hig3/C/action-bars.page      |    2 +-
 hig3/C/header-bar-menus.page |    2 +-
 hig3/C/view-switchers.page   |    2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/hig3/C/action-bars.page b/hig3/C/action-bars.page
index 75b6dfb..c56f0ae 100644
--- a/hig3/C/action-bars.page
+++ b/hig3/C/action-bars.page
@@ -20,7 +20,7 @@
 <section id="when-to-use">
 <title>When to use</title>
 
-<p>Use an action bar when content items are primarily displayed for editing or management. Since they 
prominently display potential actions, action bars are not appropriate if content is generally viewed and not 
edited. In these cases, potential actions can be placed within a <link xref="header-bar-menu">header bar 
menu</link> instead.</p>
+<p>Use an action bar when content items are primarily displayed for editing or management. Since they 
prominently display potential actions, action bars are not appropriate if content is generally viewed and not 
edited. In these cases, potential actions can be placed within a <link xref="header-bar-menus">header bar 
menu</link> instead.</p>
 
 <p>Action bars can be shown temporarily, when a <link xref="selection-mode">selection</link> or edit mode is 
active.</p>
 
diff --git a/hig3/C/header-bar-menus.page b/hig3/C/header-bar-menus.page
index bb34a4d..f989f9b 100644
--- a/hig3/C/header-bar-menus.page
+++ b/hig3/C/header-bar-menus.page
@@ -25,7 +25,7 @@
 <section id="when-to-use">
 <title>When to use</title>
 
-<p>Use a header bar menu to present additional actions or options for the current view. They are best used 
when those actions or options are not used the majority of the time - if there is a set of actions which 
deserve more prominence in the view, an <link xref="action-bar">action bar</link> might be a better 
choice.</p>
+<p>Use a header bar menu to present additional actions or options for the current view. They are best used 
when those actions or options are not used the majority of the time - if there is a set of actions which 
deserve more prominence in the view, an <link xref="action-bars">action bar</link> might be a better 
choice.</p>
 
 <p>Header bar menus are not a good choice for performing actions on selected content: when content hasn't 
been selected, the menu will contain unhelpful insensitive menu items, when it has been selected, possible 
actions will not be advertised. <link xref="selection-mode">Selection mode</link> or <link 
xref="popovers">popovers</link> are a better choice for this situation.</p>
 
diff --git a/hig3/C/view-switchers.page b/hig3/C/view-switchers.page
index 19a66a2..32bfd9b 100644
--- a/hig3/C/view-switchers.page
+++ b/hig3/C/view-switchers.page
@@ -27,7 +27,7 @@
 <item><p>If your application provides discrete groups of functionality which are typically used 
independently.</p></item>
 </list>
 
-<p>As a rule of thumb, a view switcher should contain between three and five views. If you have more views, 
a <link xref="sidebars">sidebar</link> list might be a more appropriate view switching control.</p>
+<p>As a rule of thumb, a view switcher should contain between three and five views. If you have more views, 
a <link xref="sidebar-lists">sidebar list</link> might be a more appropriate view switching control.</p>
 
 </section>
 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]