docs: minor fixes

docs/guide/genymotion-saas.mdx

@@ -215,11 +215,10 @@ We plan to improve this behavior and secure emergency teardown someday, but befo
 should be resolved (see it below). Besides, `Ctrl+C`'ing proves to be useful when you want to leave the device active
 at some point of your test scenario and interact with it manually.
 
-### `behavior.shutdownDevice` is ignored
+### `behavior.shutdownDevice` cannot be disabled
 
-Detox CLI has [`-u, --cleanup` argument], and the behavior config has the respective [`shutdownDevice`
-property], but **none of them has effect** on Genymotion SaaS devices. Detox _always shuts them down_ in the end
-of the test session, unless you abruptly terminate its execution (see the previous caveat).
+Detox CLI has [`-u, --cleanup` argument], and the behavior config has the respective [`shutdownDevice` property], but **none of them can be effectively disabled** on Genymotion SaaS devices.
+Detox _always shuts them down_ in the end of the test session, unless you abruptly terminate its execution (see the previous caveat).
 
 In other words, you can't leave Genymotion SaaS devices up and running after your test session ends. On the ond hand,
 that reduces your chances to forget a running device. On the other hand, that doesn't allow you to keep a pool of

docs/guide/parallel-test-execution.md

@@ -1,8 +1,8 @@
 # Parallel Test Execution
 
-Detox can leverage multi worker support of JS test runners ([Jest](http://jestjs.io/docs/en/cli#maxworkers-num),  etc.).
+Detox comes out of the box with multi-worker support thanks to ([Jest's feature](http://jestjs.io/docs/en/cli#maxworkers-num),  etc.).
 
-By default `detox test` will run the test runner with one worker. Worker count can be controlled by adding `--maxWorkers <N>` to `detox test`, read more in [`detox-cli` section](../cli/test.md).
+By default `detox test` will run the test runner with one worker. Worker count can be controlled by forwarding `--maxWorkers <N>` to Jest via [`detox test`](../cli/test.md).
 
 ## Device Creation
 

docs/guide/proguard-configuration.md

@@ -21,23 +21,25 @@ To fix that, you’d need to return to your app build script:
      …
 // highlight-next-line
          release {
-             minifyEnabled true
+             minifyEnabled true /* (1) */
 
 // highlight-next-line
-             proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
+   /* (2) */ proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
 // highlight-next-line
-+            proguardFile "${rootProject.projectDir}/../node_modules/detox/android/detox/proguard-rules-app.pro"
++  /* (3) */ proguardFile "${rootProject.projectDir}/../node_modules/detox/android/detox/proguard-rules-app.pro"
          }
      }
 ```
 
-1. `release` build type is usually expected to have ProGuard enabled
-1. Typical pro-guard definitions. Check out Android docs to get to know more.
-1. Detox-specific additions to pro-guard
+1. `release` build type is typically the one to have ProGuard enabled.
+1. ProGuard files present by default in React Native projects. Check out Android docs to get to know more.
+1. Detox-specific [exclude list](https://github.com/wix/Detox/blob/master/detox/android/detox/proguard-rules.pro) for ProGuard.
 
-:warning: **Note:** In order for Detox to be able to work properly, in `proguard-rules-app.pro`,
-it effectively declares rules that retain most of React-Native’s code
-(i.e. keep it unminified, unobfuscated) in your **production** APK.
+:::info
+
+In order for Detox to be able to work properly, in `proguard-rules-app.pro`, it effectively declares rules that retain most of React-Native’s code (i.e. keep it unminified, unobfuscated) in your **production** APK.
+
+:::
 
 Though generally speaking, this should not be an issue (as React-Native is an open-source project),
 there are ways around that, if it bothers you.