[Initiatives.wiki] Update DevOps with Flatpak

[Jordan Petridis <jpetridis src gnome org>]

commit aee8d633643160ad7a692d08251049c7fc272e3d
Author: Jordan Petridis <jpetridis gnome org>
Date:   Mon Dec 2 15:22:53 2019 +0000

    Update DevOps with Flatpak

 DevOps-with-Flatpak.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
---
diff --git a/DevOps-with-Flatpak.md b/DevOps-with-Flatpak.md
index 973371d..4544742 100644
--- a/DevOps-with-Flatpak.md
+++ b/DevOps-with-Flatpak.md
@@ -345,6 +345,6 @@ This almost does what we would want, but not quite. If you build this way it wil
 To achieve this we use the `--stop-at=module` argument which will build all of the dependencies up to your 
module from the manifest. Then we take over and need to install the application ourselves. This is why your 
config
 s `CONFIGURE_ARGS` variable needs to be kept in sync with your module's config options in the manifest.
 
-**A previous version of the template had some extra `review` and `stop_review` jobs, what happened to those.
+**A previous version of the template had some extra `review` and `stop_review` jobs, what happened to 
those?**
 
 They have been deprecated and replaced by a simpler feature that provides the same function. It should 
simplifies both the template setup, and the backend setup needed to run the previous jobs. For more you can 
refer to this 
[commit](https://gitlab.gnome.org/GNOME/citemplates/commit/544836ee58f91a735616ecb04ea857a66d2bb699)
\ No newline at end of file