chore: address PR reviews

.github/workflows/build-binaries.yml

@@ -55,7 +55,7 @@ jobs:
         # no need to dedup yarn.lock on all platforms
         uses: ./actions/deduplicate_fail
 
-        # we want to test on all platforms are some are testing the menus rendered (and are depent on the platform)
+        # we want to test on all platforms since some are testing the rendered menus (and are dependent on the platform)
       - name: Unit Test
         run: yarn test
 
@@ -93,7 +93,7 @@ jobs:
         with:
           cache_suffix: 'windows_x64'
 
-        # we want to test on all platforms are some are testing the menus rendered (and are depent on the platform)
+        # we want to test on all platforms since some are testing the rendered menus (and are dependent on the platform)
       - name: Unit Test
         run: yarn test
 
@@ -136,7 +136,7 @@ jobs:
         with:
           cache_suffix: 'macos_x64'
 
-        # we want to test on all platforms are some are testing the menus rendered (and are depent on the platform)
+        # we want to test on all platforms since some are testing the rendered menus (and are dependent on the platform)
       - name: Unit Test
         run: yarn test
 

CONTRIBUTING.md

@@ -274,3 +274,5 @@ You can build a production binary by running the following:
 yarn build-everything
 yarn build-release
 ```
+
+On linux, you can change in package.json `"target": ["deb"],` to any of the [electron-builder targets](https://www.electron.build/linux#target) to build for another target.

INTERNALBUILDS.md

@@ -146,3 +146,5 @@ yarn build-release
 ```
 
 The binaries will be placed inside the `release/` folder.
+
+On linux, you can change in package.json `"target": ["deb"],` to any of the [electron-builder targets](https://www.electron.build/linux#target) to build for another target.