Docs: Drop use of indexterm tags

These have not been making it into the index, anyway.

diff --git a/gio/gasyncresult.c b/gio/gasyncresult.c
index 3d9848c136ec856074d1db40bb4a3c2786ed4658..b14669792ef4bd540c8606fff7894be25fd32f89 100644 (file)
--- a/gio/gasyncresult.c
+++ b/gio/gasyncresult.c
@@ -102,15 +102,15 @@
  * always called, even in the case of a cancelled operation. On cancellation
  * the result is a %G_IO_ERROR_CANCELLED error.
  *
- * <para id="io-priority"><indexterm><primary>I/O
- * priority</primary></indexterm> Many I/O-related asynchronous
- * operations have a priority parameter, which is used in certain
- * cases to determine the order in which operations are executed.
- * They are not used to determine system-wide I/O scheduling.
- * Priorities are integers, with lower numbers indicating higher priority.
- * It is recommended to choose priorities between %G_PRIORITY_LOW and
- * %G_PRIORITY_HIGH, with %G_PRIORITY_DEFAULT as a default.</para>
- **/
+ * <para id="io-priority">
+ * Many I/O-related asynchronous operations have a priority parameter,
+ * which is used in certain cases to determine the order in which
+ * operations are executed. They are not used to determine system-wide
+ * I/O scheduling. Priorities are integers, with lower numbers indicating
+ * higher priority. It is recommended to choose priorities between
+ * %G_PRIORITY_LOW and %G_PRIORITY_HIGH, with %G_PRIORITY_DEFAULT
+ * as a default.</para>
+ */
 
 typedef GAsyncResultIface GAsyncResultInterface;
 G_DEFINE_INTERFACE (GAsyncResult, g_async_result, G_TYPE_OBJECT)

diff --git a/gio/gfile.c b/gio/gfile.c
index 9dab65bba974175aae9a39d748aa3d5e5377f178..c24bf3854556b6583dc19494d57650ff1ad2644b 100644 (file)
--- a/gio/gfile.c
+++ b/gio/gfile.c
@@ -137,12 +137,12 @@
  * <member>g_file_eject_mountable_with_operation() to eject a mountable file.</member>
  * </simplelist>
  *
- * <para id="gfile-etag"><indexterm><primary>entity tag</primary></indexterm>
+ * <para id="gfile-etag">
  * One notable feature of #GFiles are entity tags, or "etags" for
  * short. Entity tags are somewhat like a more abstract version of the
- * traditional mtime, and can be used to quickly determine if the file has
- * been modified from the version on the file system. See the HTTP 1.1
- * <ulink url="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html">specification</ulink>
+ * traditional mtime, and can be used to quickly determine if the file
+ * has been modified from the version on the file system. See the
+ * HTTP 1.1 <ulink url="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html">specification</ulink>
  * for HTTP Etag headers, which are a very similar concept.
  * </para>
  **/