More suggestions from @gnzlbg

documents/wg-application.md

@@ -5,11 +5,12 @@
 The Working Group's goal is to deliver first-class CUDA support to Rust users - see our [Roadmap].
 
 [Roadmap]: https://github.com/rust-cuda/wg/blob/master/documents/roadmap.md
+
 The work that will be done is supposed to clear the path for other GPGPU platforms in future.
 
 ## Why should it be put into place?
 
-The WG is already in place as an unofficial WG, see our [Github], [Roadmap], [Zulip], and some PRs by WG members: [rust@denzp], [rust@peterhj],  [stdsimd], [libc], etc. 
+The WG is already in place as an unofficial WG, see our [Github], [Roadmap], [Zulip], and some PRs by WG members: [rust@denzp], [rust@peterhj], [stdsimd], [libc], etc.
 
 Being an official WG would allow us to use the official communication channels like the rust-lang zulip, which would give us more visibility and allow us to attract more contributors.
 
@@ -19,11 +20,10 @@ Being an official WG would allow us to use the official communication channels l
 [stdsimd]: https://github.com/rust-lang-nursery/stdsimd/pulls?q=is%3Apr+nvptx+is%3Aclosed
 [rust@denzp]: https://github.com/rust-lang/rust/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aclosed+author%3Adenzp
 [rust@peterhj]: https://github.com/rust-lang/rust/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aclosed+author%3Apeterhj
-Regardless of recent progress, there are still a lot of questions about safety and soundness of SIMT (Single Instruction, Multiple Threads) code and they require a lot of collaboration to find solutions.
 
 ## What is the working group about?
 
-Right now, this WG is about making the already-existing Rust CUDA support minimally reliable. 
+Right now, this WG is about making the already-existing Rust CUDA support minimally reliable.
 Getting a safe and production-ready development experience on Stable Rust is our primary goal!
 
 Also, currently a major obstacle for developing GPGPU applications and algorithms in Rust is a lack of learning resources.
@@ -37,7 +37,7 @@ This WG is only about CUDA support - other GPGPU targets are out-of-scope. Our f
 
 ## Is your WG long-running or temporary?
 
-The CUDA WG is long-running. We have a [Roadmap] for an MVP, but there are many issues worth solving once that MVP is achieved (e.g. foundational libraries). 
+The CUDA WG is long-running. We have a [Roadmap] for an MVP, but there are many issues worth solving once that MVP is achieved (e.g. foundational libraries).
 
 In the end, we hope the WG will evolve into another one to cover similar topics:
 to support other GPGPU platforms or to create higher-level frameworks to improve end-to-end experience based on community feedback.
@@ -65,8 +65,8 @@ Once we achieve important milestones we plan to make public announces.
 
 ## Which other WGs do you expect to have close contact with?
 
-We would like to cooperate with Core or Compiler Teams in discussions about safety in SIMT code.
-Additionally, it would be very important to discuss a strategy of reliable deployment of `rust-ptx-linker` (likely as a `rustup` component).
+We would like to cooperate with *Language Team* in discussions about safety in SIMT code.
+Additionally, it would be very important to discuss with *Infra team* a strategy of reliable deployment of `rust-ptx-linker` (likely as a `rustup` component).
 
 On the other hand, proposed [Machine Learning WG](https://internals.rust-lang.org/t/enabling-the-formation-of-new-working-groups/10218/11) could leverage CUDA accelerated computing capabilities, so we can discuss their use cases.
 
@@ -95,10 +95,6 @@ We work in the open, see our [Github].
 
 > TBD... would it make sense to move to a `rust-lang` Zulip server?
 
-## Where do you need help?
-
-> TBD...
-
 ## Preferred way of contact/discussion
 
 [Github] issues or [Zulip].