[Initiatives.wiki] Update DevOps with Flatpak

[Carlos Soriano <csoriano src gnome org>]

commit 63a4d7349b09732d310ca3e8b57b6c5279896665
Author: Carlos Soriano <csoriano1618 gmail com>
Date:   Sat Aug 4 06:06:39 2018 +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 83152cf..75a5c46 100644
--- a/DevOps-with-Flatpak.md
+++ b/DevOps-with-Flatpak.md
@@ -81,7 +81,7 @@ And finally we want to expose the build in the MR using GitLab Review Apps. To d
 
 There are 2 `except:` keys with one of the values being `master@GNOME/project-url`. You will need to replace 
`project-url` with the path of you module, can be found by looking at the url of the project. For example for 
`nautilus`, with project url `gitlab.gnome.org/GNOME/nautilus`, this value is [set][except_master] to 
`master@GNOME/nautilus`.
 
-This is done so we can avoid setting up environments for the master branch of the project since there will 
be no Merge Requests made from it. Gitlab Environments can be expensive and long lived operations so make 
sure you get this right please. Note that the CI will still produce and make available flatpak bundles from 
the `master` branch. There will just not be a fancy link for it and you would have to look on the CI/job logs 
to get the bundle(s).
+This is done so setting up environments for the master branch of the project can be avoided since there will 
be no Merge Requests made from it. This is particularly useful since Gitlab Environments are full Docker 
environments which takes considerable resources. Note that the CI will still produce and make available 
Flatpak bundles from the `master` branch accessible on the CI/job logs, it won't just create a deployment for 
it.
 
 ```yaml
 review: