[gimp-web/testing] Small fixes on the 2.10.6 news.

[Jehan <jehanp src gnome org>]

commit e53e8ce623fa470afabd0fe57c724b5aa4bedf2e
Author: Jehan <jehan girinstud io>
Date:   Thu Aug 16 19:06:49 2018 +0200

    Small fixes on the 2.10.6 news.
    
    Most notable is that I think what is expensive with layer group preview
    is that they are not rendered asynchronously, unlike end layers (and not
    that they are rendered asynchronously but that it still somehow slows
    the GUI down).
    At least that's how I understand this commit message on GIMP (I have not
    digged enough into the code to confirm myself):
    commit 0d2d45c3ef5e0a5c1ba030473ba6c9f5a96f0ef6
    We should ask Ell to clarify.

 content/news/2018-08_GIMP-2.10.6_Released/index.md | 21 ++++++++++-----------
 1 file changed, 10 insertions(+), 11 deletions(-)
---
diff --git a/content/news/2018-08_GIMP-2.10.6_Released/index.md 
b/content/news/2018-08_GIMP-2.10.6_Released/index.md
index b3c2a22a..65225678 100644
--- a/content/news/2018-08_GIMP-2.10.6_Released/index.md
+++ b/content/news/2018-08_GIMP-2.10.6_Released/index.md
@@ -102,14 +102,14 @@ by specifying explicitly which it should be.
 
 Most creators working on complex projects in GIMP have had bad days when there
 are many layers in a large image, and GIMP can't keep up with scrolling the
-layers list of showing/hiding layers.
+layers list or showing/hiding layers.
 
 Part of the reason was that GIMP couldn't update user interface until it was
 done rendering layer previews. Ell again did some miracles here by having most
 drawable previews render asynchronously.
 
 For now, the only exception to that are layer groups. Rendering them
-asynchronously is still very expensive, so until we deal with this too, we made
+asynchronously is still not possible, so until we deal with this too, we made
 it possible for you to disable rendering layer group previews completely. Head
 over to _Preferences > Interface_ and tick off the respective checkbox.
 
@@ -185,7 +185,7 @@ libraries interfering with other plug-ins.
 The former had already been mostly fixed by tweaking the DLL search priority
 order. This release provides an additional fix by taking into account 32-bit
 plug-ins running on 64-bit Windows systems
-([WoW64 mode](https://en.wikipedia.org/wiki/WoW64).
+([WoW64 mode](https://en.wikipedia.org/wiki/WoW64)).
 
 The latter was fixed already since GIMP 2.10.0 **if** you installed your
 plug-ins in its own directory (which is not compulsory yet, but will be in
@@ -207,15 +207,14 @@ invasion](https://www.patreon.com/posts/20264674)" in babl and GEGL, our
 graphics engine, making our core now internally color-managed. Mitch on
 his side has been integrating such changes in GIMP itself.
 
-TODO: screenshot?
-
 Lastly Jehan, from [ZeMarmot project](https://www.patreon.com/zemarmot),
-have been working on extensions in GIMP. An extension could be anything
-from plug-ins to splash images, patterns, brushes, gradients… Basically
-anything which could be created and added by anyone. The end goal would
-be to allow creators of such extensions to upload them on public
-repositories, and for anyone to search and install them in a few clicks,
-with version management, updates, etc.
+have been working on [extensions in
+GIMP](https://girinstud.io/news/2018/07/crowdfunding-for-extension-management-in-gimp-and-other-improvements/).
+An extension could be anything from plug-ins to splash images, patterns,
+brushes, gradients… Basically anything which could be created and added
+by anyone. The end goal would be to allow creators of such extensions to
+upload them on public repositories, and for anyone to search and install
+them in a few clicks, with version management, updates, etc.
 
 TODO: screenshot.