Fixes formatting and adds requirement for Cloud Patches

Author: jkelroy

gitkraken-client/experimental-features.md

@@ -119,7 +119,12 @@ Cloud Patches allow the ability to engage early with your team before a pull req
 
 #### How to setup Cloud Patches
 
-To enable Cloud Patches in GitKraken Client, check `Use Cloud Patches` under `Preferences > Experimental`. To disable Cloud Patches per client, simply uncheck this option.
+To enable Cloud Patches in GitKraken Client, navigate to `Preferences > Experimental` and check the following options:
+
+- `Use Cloud Patches`
+- `Use Git Executable`
+
+To disable Cloud Patches per client, simply uncheck `Use Cloud Patches`.
 
 #### How to work with Cloud Patches
 
@@ -141,10 +146,10 @@ To delete a cloud path, right-click it and select `Delete Cloud Patch`.
 
 We offer the ability for you to host Cloud Patches on your own AWS S3 storage instances. In order to set this up, please reach out to our [support team](https://help.gitkraken.com/gitkraken-client/contact-support/) and include the following information about your bucket:
 
- - Name of AWS bucket
- - AWS region the bucket is located in
+- Name of AWS bucket
+- AWS region the bucket is located in
 
- Once we have that information, we will provide you with a bucket policy that can be attached to your bucket through the Permissions Bucket Policy Editor. After that is completed, Cloud Patches will be stored on your own bucket. 
+Once we have that information, we will provide you with a bucket policy that can be attached to your bucket through the Permissions Bucket Policy Editor. After that is completed, Cloud Patches will be stored on your own bucket. 
 
 ---