[gtk/matthiasc/glshader-node] gsk: Tweak GskGLShader long desc

[Matthias Clasen <matthiasc src gnome org>]

commit ec2a5600415c0bb59c0f210f021555e8db96606a
Author: Matthias Clasen <mclasen redhat com>
Date:   Mon Sep 28 14:00:38 2020 -0400

    gsk: Tweak GskGLShader long desc
    
    Reformulate one paragraph, as suggested by Benjamin.

 gsk/gskglshader.c | 14 ++++++--------
 1 file changed, 6 insertions(+), 8 deletions(-)
---
diff --git a/gsk/gskglshader.c b/gsk/gskglshader.c
index bc3feca245..e3a944866b 100644
--- a/gsk/gskglshader.c
+++ b/gsk/gskglshader.c
@@ -30,14 +30,12 @@
  * each instance of use). A shader can also receive up to 4
  * textures that it can use as input when producing the pixel data.
  *
- * The typical way a #GskGLShader is used is as an argument to a
- * #GskGLShaderNode in the rendering hierarchy, and then the textures
- * it gets as input are constructed by rendering the child nodes to
- * textures before rendering the shader node itself. (Although you can
- * also pass texture nodes as children if you want to directly use a
- * texture as input). Note that the #GskGLShaderNode API is a bit
- * lowlevel, and highlevel code normally uses
- * gtk_snapshot_push_glshader() to produce the nodes.
+  #GskGLShader is usually used with gtk_snapshot_push_gl_shader()
+* to produce a #GskGLShaderNode in the rendering hierarchy, and then
+* its input textures are constructed by rendering the child nodes to
+* textures before rendering the shader node itself. (You can pass
+* texture nodes as children if you want to directly use a texture
+* as input).
  *
  * The actual shader code is GLSL code that gets combined with
  * some other code into the fragment shader. Since the exact