[gimp-web/testing] Fixes to the news item, suggested by patdavid

[Alexandre Prokoudine <aprokoudine src gnome org>]

commit d62eeadde2151c3b31c50e49e964bc8fe71b83d5
Author: Alexandre Prokoudine <alexandre prokoudine gmail com>
Date:   Mon May 23 23:56:22 2016 +0300

    Fixes to the news item, suggested by patdavid

 .../news/2016-05-23 Documentation Update Call.md   |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/content/news/2016-05-23 Documentation Update Call.md b/content/news/2016-05-23 Documentation 
Update Call.md
index ca36824..f0e4592 100644
--- a/content/news/2016-05-23 Documentation Update Call.md      
+++ b/content/news/2016-05-23 Documentation Update Call.md      
@@ -6,7 +6,7 @@ Status: draft
 Slug: gimp-2-10-docs-update-call
 Summary: For the past several months we've been working on GIMP mostly in the bugfix mode. It's time to 
start updating the user manual for the upcoming release.
 
-With upcoming GIMP 2.10 release we intend to finally close the time gap between releases of source code, 
installers, and the user manual. This means that we need a more coordinated effort between the GIMP 
developers team and the GIMP User Manual team.
+With the upcoming GIMP 2.10 release we intend to finally close the time gap between releases of source code, 
installers, and the user manual. This means that we need a more coordinated effort between the GIMP 
developers team and the GIMP User Manual team.
 
 For the past several months we've already been working on GIMP mostly in bugfix mode. It's time to start 
updating the user manual to match all the changes in GIMP 2.10, and we would appreciate your help with that.
 
@@ -21,9 +21,9 @@ For the past several months we've already been working on GIMP mostly in bugfix
 
 Technical documentation on hacking on the user manual is 
[available](https://git.gnome.org/browse/gimp-help-2/tree/HACKING) in the respective Git repository.
 
-The primary communication environment for all things documentation in the project is the [gimp-docs 
](https://mail.gnome.org/mailman/listinfo/gimp-docs-list) mailing list. We encourage you to talk to fellow 
team members publicly about which part of the documentation you are hacking on. This is because efficient 
collaboratove effort requires full transparence.
+The primary communication environment for all things documentation in the project is the [gimp-docs 
](https://mail.gnome.org/mailman/listinfo/gimp-docs-list) mailing list. We encourage you to talk to fellow 
team members publicly about which part of the documentation you are hacking on. This is because efficient 
collaborative effort requires full transparence.
 
 If you have technical questions about features in GIMP 2.10, you can use either gimp-docs@ mailing list or 
join the [IRC channel](http://www.gimp.org/irc.html), ask your question, and stick around for the answer.
 
-We do not yet have an estimated time of arrival for GIMP 2.10, but there's only so much time we can spend on 
tieing loose ends before we can move to the next development cycle.
+We do not yet have an estimated time of arrival for GIMP 2.10, but there's only so much time we can spend on 
completing this release before we can move to the next development cycle.