Updated FLATPAK.md outdated text

Author: ebkr

FLATPAK.md

@@ -40,10 +40,10 @@ Getting Flatpak to invoke Steam has been rough. Steam, when launched from a Flat
 
 So what's the fix?
 
-The best solution I've come up with so far, and at the time of writing is yet to work fully, is to have a wrapper script that reads additional arguments via a separate file. Since we're doing things this way, it means we can also use the `steam://` protocol as we don't need to pass any additional arguments to the game process anymore, and we let the xdg handle opening the executable. It also means it likely works with Steam installed via Flatpak as we don't try to start multiple instances.
+The best solution I've come up with so far is to have a wrapper script that reads additional arguments via a separate file. Since we're doing things this way, it means we can also use the `steam://` protocol as we don't need to pass any additional arguments to the game process anymore, and we let the xdg handle opening the executable. It also means it likely works with Steam installed via Flatpak as we don't try to start multiple instances.
 
 ### Quirks
 
 Unrelated though because it's not used anymore, but Node really doesn't like calling `flatpak-spawn`. Using `child_process` to call a separate script which then calls flatpak-spawn is fine and launches as expected, but calling it directly from the `child_process` library always fails to find it. Potentially weird sandboxing from Node?
 
-Calling via flatpak-spawn seemed to launch Steam under a minimally sandboxed environment, and so additional permissions were needed to be passed so that audio could be accessed from within the client. Weirdly, if you already had Steam open however, the one running under the host would be used instead. It may be related to my Flatpak version or some odd Node quirk, or maybe even something I've done without realising.
+Calling via flatpak-spawn seemed to launch Steam under a minimally sandboxed environment, and so additional permissions were needed to be passed so that audio could be accessed from within the client. Weirdly, if you already had Steam open however, the one running under the host would be used instead. It may be related to my Flatpak version or some odd Node quirk, or maybe even something I've done without realising.