RGBA: Consistently use “” around inline arg names

instead of being inconsistent and not using them later, which leaves a
bunch of single letters floating among real words, not the prettiest.

1 files changed, 4 insertions, 4 deletions

diff --git a/gdk/gdkrgba.c b/gdk/gdkrgba.c
index fe82773f14..c301b8ee0e 100644
--- a/gdk/gdkrgba.c
+++ b/gdk/gdkrgba.c
@@ -175,7 +175,7 @@ parse_rgb_value (const gchar  *str,
  * - A RGBA color in the form “rgba(r,g,b,a)”
  *
  * Where “r”, “g”, “b” and “a” are respectively the red, green, blue and
- * alpha color values. In the last two cases, r g and b are either integers
+ * alpha color values. In the last two cases, “r”, “g”, and “b” are either integers
  * in the range 0 to 255 or percentage values in the range 0% to 100%, and
  * a is a floating point value in the range 0 to 1.
  *
@@ -356,15 +356,15 @@ gdk_rgba_equal (gconstpointer p1,
  * `rgb(r,g,b)` or
  * `rgba(r g,b,a)`,
  * where “r”, “g”, “b” and “a” represent the red, green,
- * blue and alpha values respectively. r, g, and b are
- * represented as integers in the range 0 to 255, and a
+ * blue and alpha values respectively. “r”, “g”, and “b” are
+ * represented as integers in the range 0 to 255, and “a”
  * is represented as floating point value in the range 0 to 1.
  *
  * These string forms are string forms those supported by
  * the CSS3 colors module, and can be parsed by gdk_rgba_parse().
  *
  * Note that this string representation may lose some
- * precision, since r, g and b are represented as 8-bit
+ * precision, since “r”, “g” and “b” are represented as 8-bit
  * integers. If this is a concern, you should use a
  * different representation.
  *