[libsoup] Fix documentation to use the appropriate term for flags

[Gustavo Noronha Silva <gns src gnome org>]

commit 2d05a8d1e75599970a502819eb0cf32381b478f3
Author: Gustavo Noronha Silva <gustavo noronha collabora com>
Date:   Tue Sep 13 13:44:43 2011 -0300

    Fix documentation to use the appropriate term for flags
    
    Although checking for the existence of flags yields a boolean value,
    flags can't be true, they are either set or not set.

 libsoup/soup-message.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/libsoup/soup-message.c b/libsoup/soup-message.c
index 9aa1209..5cd4ac8 100644
--- a/libsoup/soup-message.c
+++ b/libsoup/soup-message.c
@@ -1427,7 +1427,7 @@ soup_message_cleanup_response (SoupMessage *req)
  *   indicate that it has removed the Content-Encoding on a message (and
  *   so headers such as Content-Length may no longer accurately describe
  *   the body).
- * @SOUP_MESSAGE_CERTIFICATE_TRUSTED: if %TRUE after an https response
+ * @SOUP_MESSAGE_CERTIFICATE_TRUSTED: if set after an https response
  *   has been received, indicates that the server's SSL certificate is
  *   trusted according to the session's CA.
  *