[gimp-web] content: various fixes, as reported by Jacob.

[Jehan <jehanp src gnome org>]

commit 032e1705b780a2dd824aeec68cb3b3f90bf5c7a8
Author: Jehan <jehan girinstud io>
Date:   Thu Aug 25 21:32:35 2022 +0200

    content: various fixes, as reported by Jacob.

 .../2022/2022-08_GIMP-2.99.12_Released/index.md    | 44 +++++++++++-----------
 1 file changed, 22 insertions(+), 22 deletions(-)
---
diff --git a/content/news/2022/2022-08_GIMP-2.99.12_Released/index.md 
b/content/news/2022/2022-08_GIMP-2.99.12_Released/index.md
index 095022e7..48d808bb 100644
--- a/content/news/2022/2022-08_GIMP-2.99.12_Released/index.md
+++ b/content/news/2022/2022-08_GIMP-2.99.12_Released/index.md
@@ -7,7 +7,7 @@ Summary: Release news for development version GIMP 2.99.12
 Image: gimp-2-99-10-20220221-experiments.jpg
 
 GIMP 2.99.12 is a huge milestone towards GIMP 3.0. Many of the missing
-pieces are getting together, even though it is still work in progress.
+pieces are getting together, even though it is still a work in progress.
 As usual, issues are expected and possibly in particular in this release
 which got important changes in major areas, such as canvas interaction
 code, scripts, but also theming…
@@ -35,7 +35,7 @@ So we went for direct and quick brush size change for instance.
 
 TODO: explain how it works and small animated image.
 
-Note that there are still work-in-progress in this area. There are also
+Note that this area still is a work-in-progress. There are also
 interactions worked on, such as opacity update and even much more (see
 [next section](#customizable-on-canvas-modifiers)); right now it doesn't
 feel exactly right.
@@ -65,10 +65,10 @@ The current features are:
 
 These are based on the following logic:
 
-* the main button is reserved for tools. Even though some of them share
+* The main button is reserved for tools. Even though some of them share
   similar logic (e.g. all the selection tools have similar modifier use
   to add/subtract/intersect selections), some may have pretty unique
-  need. So the tool does not touch this private area
+  need. So the tool does not touch this private area.
 * Then the secondary button was used for "navigation", in particular
   canvas navigation, but even on some kind of `z` axis with layer
   navigation with the recent Layer picking.
@@ -77,15 +77,15 @@ These are based on the following logic:
 
 As we added new features, it became obvious that we were eventually
 going to lack enough identifiers for other useful actions. Also everyone
-is different and have different workflows so some people would
-definitely prefer to have slightly different action behavior. As an
-example, even the [just implemented brush
+is unique and has their own preferred workflow, so some people would
+definitely prefer to have slightly different action behavior.
+As an example, even the [just implemented brush
 sizing](#on-canvas-brush-sizing) already comes in 2 variants.
 
 Not to mention it was starting to get crowded and we had feedbacks
 lately of people disliking some canvas actions happening unexpectedly,
 for instance because they hit `Shift` too early and a canvas rotation
-happens (and admittedly not anyone care about having canvas rotation in
+happens (and admittedly not everyone cares about having canvas rotation in
 their workflow).
 Some legacy actions, such as a contextual menu on right click can also
 be questionable nowadays (especially as it is the same menu available
@@ -265,11 +265,11 @@ As many other projects, GIMP was using the `intltool` project to extract
 localizable strings and translate various files with `gettext`, not only
 code.
 
-Since about 2016, upstream `gettext` gained ability to extract strings
-for more types of files and formats, projects were [encouraged to move
-on](https://wiki.gnome.org/MigratingFromIntltoolToGettext) and the
-`intltool` project was progressively abandoned. But GIMP was still using
-it for various types of files (XML, desktop files, Inno Setup
+Since about 2016, upstream `gettext` gained the ability to extract
+strings for more types of files and formats, projects were [encouraged
+to move on](https://wiki.gnome.org/MigratingFromIntltoolToGettext) and
+the `intltool` project was progressively abandoned. But GIMP was still
+using it for various types of files (XML, desktop files, Inno Setup
 translation files and more…) so the workfield was not small.
 
 Well no more as Niels De Graef finally took care of this port and got
@@ -330,8 +330,8 @@ macOS versions (ever since Big Sur). We had some custom patches already
 for GTK and some dirty trick in GIMP code itself since [GIMP
 2.99.10](https://www.gimp.org/news/2022/02/25/gimp-2-99-10-released/#wayland-and-macos-support).
 
-It all led to some much better improvements in GTK code which took over
-the previous patches. It took months of testing, several code proposals
+It all led to various improvements in GTK code which took over the
+previous patches. It took months of testing, several code proposals
 in several directions (at least 3 different merge requests, possibly
 more code was discarded) and it got to a very satisfying result as Lukas
 confirmed it is much faster now and GIMP is totally usable. Our in-GIMP
@@ -521,7 +521,7 @@ wants to contribute to the documentation, you should look at the
 propose merge requests. The contribution format is *DocBook*.
 
 For translation contributions, you should get in touch with GNOME
-translation teams as they have their own platform. More information are
+translation teams as they have their own platform. More information is
 available [here](https://docs.gimp.org/help.html).
 
 A dedicated news with more details on the change might soon be
@@ -534,7 +534,7 @@ other platforms and for packagers, containing up-to-date contents.
 Meanwhile our [developer website](https://developer.gimp.org/) was in an
 even more dire situation as it had not been updated for over 10 years!
 
-This is about to change as one of our goal for GIMP 3.0 is to improve
+This is about to change as one of our goals for GIMP 3.0 is to improve
 the plug-in ecosystem, not only with an upcoming [extension
 platform](https://www.gimp.org/news/2020/11/06/gimp-2-99-2-released/#extensions),
 but also with better and more up-to-date documentation.
@@ -555,7 +555,7 @@ wiki.
 Ah, the wiki! Some people might have noticed that it is gone now. We
 used to have the roadmap, build instructions for newcomers and more
 technical or historical stuff over there. Let's say that unfortunate
-events occured, and we lost it. 😱
+events occurred, and we lost it. 😱
 
 Fortunately all the contents could be salvaged, and we are now going to
 port what is the valuable parts into the upcoming developer website,
@@ -711,10 +711,10 @@ Other packages made by third-party are obviously expected to follow
 
 ## What's next
 
-This release is once again a major milestone towards GIMP 3.0. Every
-2.99 development versions were big milestones, but now we are really
-feeling we are getting close to release candidates with some great
-improvements happening in much needed places:
+This release is once again a major milestone towards GIMP 3.0. All 2.99
+development versions were big milestones, but now we are really feeling
+we are getting close to release candidates with some great improvements
+happening in much needed places:
 
 * we are finally getting proper neutral-gray themes;
 * our Wayland build is finally getting a bit stabler (even though issues remain);