[gimp-web] content: various fixes.

[Jehan <jehanp src gnome org>]

commit 778b27c7c7da61485ce6f58dc2045724bf43a33e
Author: Jehan <jehan girinstud io>
Date:   Sat Aug 27 00:02:12 2022 +0200

    content: various fixes.
    
    Also only cite Lloyd once, then use "we" or generic wording, as it made
    him a bit uncomfortable (cf. his review on IRC).

 .../2022/2022-08_GIMP-2.99.12_Released/index.md    | 35 +++++++++++-----------
 1 file changed, 18 insertions(+), 17 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 1b9b4a4e..6b2c41f7 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
@@ -677,50 +677,51 @@ responsibility to heart as Script-fu code has not seen such activity for
 years now.
 
 A lot of bugs were fixed, more documentation for Script-fu developers
-was written, but also a lot of huge change happened.
+was written, but also a lot of huge changes happened.
 
 ### Script-fu server now its own plug-in
 
 Script-fu used to be a very monolithic extension plug-in (i.e. a plug-in
-running permanently in background), with all its features in one binary.
-It had several drawbacks. One of them is that the Script-fu server
-(`script-fu-server`), which allows to communicate with GIMP remotely.
+running permanently in background), with all its features in one binary,
+which had several drawbacks. One of them is that the Script-fu server
+(`script-fu-server`), which allows to communicate with GIMP remotely,
+would also be running in the same process.
 
-It can be considered a security hazard, which is why Lloyd made it its
-own plug-in, which can be run independently, on request only.
+It can be considered a security hazard, which is why it was made its own
+plug-in, which can be run independently, on request only.
 
 ### New separate interpreter
 
 GIMP now installs a `gimp-script-fu-interpreter-3.0` binary which will
 run the Script-fu scripts. It has huge advantages:
 
-* Now Script-fu scripts are proper plug-ins. They are installed within
-  the `plug-ins/` folder (not in `scripts/` anymore), and work the same
-  way as other bindings.
+* Script-fu scripts are finally proper plug-ins. They are installed
+  within the `plug-ins/` folder (not in `scripts/` anymore), and work
+  the same way as other bindings.
   Note that Script-fu is not a GObject-Introspected binding, unlike
   other bindings, and it has its own way to wrap the PDB protocol or
   `libgimp*` libraries, but other than this, it became now much closer
   conceptually.
 * It makes the Script-fu infrastructure much more robust as a single
   crashing script will not crash the whole Script-fu altogether. Every
-  Script-fu plug-in now runs in its own dedicated process and is
-  independant.
+  Script-fu plug-in now runs in its own dedicated and independant
+  process.
 
 ### Rethinking the API
 
 Since a lot happened on the main `libgimp*` API, Script-fu specific API
-had not been able to follow up. Lloyd tried to fill that gap and to get
-Script-fu much closer to the main interface.
+had not been able to follow up. We are now trying to fill that gap and
+to get Script-fu much closer to the main interface.
 
 Among these changes, the new function `script-fu-register-filter` is
 used to declare PDB procedure of the C class `GimpImageProcedure`. It
 will also allow to much more easily use the procedural dialog generation
 through the `GimpProcedureDialog` class.
 
-In other things which Lloyed helped with are the discussions on argument
-handling of various types. This is still a work-in-progress as we are
-trying to improve some use cases, for instance handling of plug-in
-specific lists of options.
+A lot of discussions also happened on the topic of argument handling for
+various types. This is still a work-in-progress as we are trying to
+improve some use cases, for instance handling of plug-in's specific
+lists of options.
 
 ## API