Updated issue templates, code of conduct, and contributing [ci skip]

.github/ISSUE_TEMPLATE/bug.md

@@ -1,6 +1,6 @@
 ---
 name: "Bug Report"
-about:  "Create a report to help us improve"
+about: "Create a report to help us improve"
 labels: type:bug
 ---
 
@@ -11,46 +11,51 @@ We're happy to help you via our support channels! Please read: https://github.co
 
 By filing an issue, you are expected to comply with our code of conduct: https://github.com/cryptomator/cryptomator/blob/develop/.github/CODE_OF_CONDUCT.md
 
-Of course we also expect you to search for existing similar issues, first! ;) https://github.com/cryptomator/cryptomator/issues?q=
+Of course, we also expect you to search for existing similar issues first! ;) https://github.com/cryptomator/cryptomator/issues?q=
 
 -->
 
 ### Description
 
-[Summarize your problem]
+[Summarize your problem.]
 
 ### System Setup
 
-* Operating system and version:
-* Cryptomator version (shown in the settings):
-* Drive (FUSE/Dokany/WebDAV):
+* Operating system and version: [Windows/macOS/Linux + Version]
+* Cryptomator version: [Shown in the settings]
+* Drive: [Dokany/FUSE/WebDAV]
 
 ### Steps to Reproduce
 
-1. [First Step]
-2. [Second Step]
-3. [and so on...]
+1. [First step]
+2. [Second step]
+3. [and so on…]
 
-#### Expected behavior:
-[What you expect to happen]
+#### Expected Behavior
 
-#### Actual behavior
-[What actually happens]
+[What you expect to happen.]
 
-#### Reproduces how often:
-[What percentage of the time does it reproduce?]
+#### Actual Behavior
+
+[What actually happens.]
+
+#### Reproducibility
+
+[Always/Intermittent/Only once]
 
 ### Additional Information
 
-Any additional information, log files, screenshots, configuration or data that might be necessary to reproduce the issue.
+[Any additional information, log files, screenshots, configuration, or data that might be necessary to reproduce the issue.]
 
 <!--
+
 If you want to add the log file or screenshots, please add them as attachments. If your log file seems empty and doesn't show any errors, you may enable the debug mode first. Here is how to do that: https://community.cryptomator.org/t/how-do-i-enable-debug-mode/36
 
 Then reproduce the problem to ensure all important information is contained in there. You may use test data or redact sensitive information from the log file.
 
-You can find the log file
-- on Windows: %appdata%/Cryptomator/cryptomator.log
-- on macOS: ~/Library/Logs/Cryptomator/cryptomator.log
-- on Linux: ~/.Cryptomator/cryptomator.log
+Log file location:
+- Windows: %appdata%/Cryptomator
+- macOS: ~/Library/Logs/Cryptomator
+- Linux: ~/.local/share/Cryptomator/logs
+
 -->

.github/ISSUE_TEMPLATE/feature.md

@@ -1,6 +1,6 @@
 ---
 name: "Feature Request"
-about:  "Suggest an idea for this project"
+about: "Suggest an idea for this project"
 labels: type:feature-request
 ---
 
@@ -11,22 +11,22 @@ We're happy to help you via our support channels! Please read: https://github.co
 
 By filing a feature request, you are expected to comply with our code of conduct: https://github.com/cryptomator/cryptomator/blob/develop/.github/CODE_OF_CONDUCT.md
 
-Of course we also expect you to search for existing similar feature requests, first! ;)
+Of course, we also expect you to search for existing similar feature requests first! ;)
 
 -->
 
 ### Summary
 
-One paragraph explanation of the feature.
+[One paragraph explanation of the feature.]
 
 ### Motivation
 
-Why are we doing this? What use cases does it support? What is the expected outcome?
+[Why are we doing this? What use cases does it support? What is the expected outcome?]
 
-### Describe alternatives you've considered
+### Considered Alternatives
 
-A clear and concise description of the alternative solutions you've considered. Be sure to explain why Atom's existing customizability isn't suitable for this feature.
+[A clear and concise description of the alternative solutions you've considered.]
 
-### Additional context
+### Additional Context
 
-Add any other context or screenshots about the feature request here.
+[Add any other context or screenshots about the feature request here.]