Fix typos, clarify steps

This commit is contained in:
Manil Chowdhury 2023-07-06 16:42:06 +03:00 committed by Alex Pyrgiotis
parent 680c57b8c5
commit a1bbcdf2b6
No known key found for this signature in database
GPG key ID: B6C15EBA0357C9AA

View file

@ -48,15 +48,15 @@ Set up a development environment by following [these instructions](/BUILD.md).
### "I'm experiencing an issue while using Dangerzone." ### "I'm experiencing an issue while using Dangerzone."
Dangerzone gets updates to improve its features _and_ to fix problems. So, updating may be the simplest path to resolving the issue. Here is how to update: Dangerzone gets updates to improve its features _and_ to fix problems. So, updating may be the simplest path to resolving the issue which brought you here. Here is how to update:
1. Check which version of Dangerzone you are currently usi: run Dangerzone, then look for the series of numbers to the left of the logo. It will look similar to `0.4.1` 1. Check which version of Dangerzone you are currently using: run Dangerzone, then look for a series of numbers to the right of the logo within the app. The format of the numbers will look similar to `0.4.1`
2. Now find the latest available version of Dangerzone: go to the [download page](https://dangerzone.rocks/#downloads). Look for the number displayed using the same format as in Step 1. 2. Now find the latest available version of Dangerzone: go to the [download page](https://dangerzone.rocks/#downloads). Look for the version number displayed. The number will be using the same format as in Step 1.
3. Is the version on the Dangerzone download page higher than the version of your installed app? Go ahead and update. 3. Is the version on the Dangerzone download page higher than the version of your installed app? Go ahead and update.
### "I get `invalid json returned from container` on MacOS Big Sur or newer (MacOS 11.x.x or higher)" ### "I get `invalid json returned from container` on MacOS Big Sur or newer (MacOS 11.x.x or higher)"
Are you using the latest Dangerzone? Are you using the latest version of Dangerzone? See the FAQ for: "I'm experiencing an issue while using Dangerzone."
You _may_ be attempting to convert a file in a directory to which Docker Desktop does not have access. Dangerzone for Mac requires Docker Desktop for conversion. Docker Desktop, in turn, requires permission from MacOS to access the directory in which your target file is located. You _may_ be attempting to convert a file in a directory to which Docker Desktop does not have access. Dangerzone for Mac requires Docker Desktop for conversion. Docker Desktop, in turn, requires permission from MacOS to access the directory in which your target file is located.