[Telepathy-commits] [telepathy-doc/master] Validity fixes

[Davyd Madeley]

---
 docs/book/C/channel.xml     |    2 +-
 docs/book/C/connection.xml  |    7 ++++---
 docs/book/C/contactinfo.xml |    6 +++---
 3 files changed, 8 insertions(+), 7 deletions(-)

diff --git a/docs/book/C/channel.xml b/docs/book/C/channel.xml
index 50799ae..8665100 100644
--- a/docs/book/C/channel.xml
+++ b/docs/book/C/channel.xml
@@ -988,7 +988,7 @@
        be heralded by the <methodname>NewChannels</methodname> signal.
        Filter on the channels given for channels of type
        <type>Channel_Type_Text</type>.
-       <xref linkend="ex.channel.text.messages.newchannels"/> shows
+       <xref linkend="ex.channel.text.messages.receiving.newchannels"/> shows
        how to discover this channel.
       </para>
 
diff --git a/docs/book/C/connection.xml b/docs/book/C/connection.xml
index f40b104..3824216 100644
--- a/docs/book/C/connection.xml
+++ b/docs/book/C/connection.xml
@@ -23,7 +23,7 @@
    A <interfacename>Connection</interfacename> object in Telepathy
    represents an active (or activatable) protocol session. Connections are
    created by the appropriate
-   <link xref="sect.connection.connection-manager">Connection Manager</link>.
+   <link linkend="sect.connection.connection-manager">Connection Manager</link>.
   </para>
 
   <para>
@@ -235,7 +235,7 @@
      <para>
       To setup your own connection to the remote server (e.g. your Jabber
       IM account) you need to call <methodname>RequestConnection</methodname>
-      on the appropriate <link xref="sect.connection.connection-manager">
+      on the appropriate <link linkend="sect.connection.connection-manager">
       Connection Manager</link> (e.g. gabble), providing a map of connection
       details. Assuming the connection succeeds this method will return the
       <literal>bus name</literal> and <literal>object path</literal>
@@ -373,8 +373,9 @@
 
      <example id="example.connection.establish-connection">
       <title>Establishing a Connection</title>
+      <para></para><!-- bodge validity -->
       <!--
-      <para><ulink url="&url_examples_base;connect">Source Code</ulink></para>
+      url="&url_examples_base;connect">
       -->
      </example>
      
diff --git a/docs/book/C/contactinfo.xml b/docs/book/C/contactinfo.xml
index 07dfe71..31c6c4c 100644
--- a/docs/book/C/contactinfo.xml
+++ b/docs/book/C/contactinfo.xml
@@ -27,14 +27,14 @@
 
  <para>
   A list of handles usually comes from a channel with the
-  <link xref="sect.channel.groups">Group</link> interface (i.e. a chatroom
-  or a <link xref="sect.channel.contactlist">contact list</link>).
+  <link linkend="sect.channel.groups">Group</link> interface (i.e. a chatroom
+  or a <link linkend="sect.channel.contactlist">contact list</link>).
  </para>
 
  <para>
   In general, a client will connect the relevant signals to receive updates
   for presence, aliases, avatars, capabilities, and so on; and then use
-  the <link xref="sect.contactinfo.contacts">Contacts</link> interface to
+  the <link linkend="sect.contactinfo.contacts">Contacts</link> interface to
   bulk request the intial state.
  </para>
   
-- 
1.5.6.5