fix: update issue templates for consistency and clarity

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,33 +1,39 @@
 ---
 name: Bug report
 about: Report a problem
-title: ''
+title: ""
 labels: pending review
 assignees: Azgaar
-
 ---
 
-<!-- PLEASE FILL OUT THE FOLLOWING INFORMATION -->
 **Describe the bug**
+
 <!-- A clear and concise description of what the bug is -->
 
 **Steps to reproduce**
+
 <!-- Steps to reproduce the behavior. Please try to explain like to a 5-year-old person who had never used the tool before -->
+
 1. Click on ...
 2. Type ...
 3. See the ...
 
 **Expected behavior**
+
 <!-- A clear and concise description of what you expected to happen -->
 
 **.map file**
+
 <!-- Attach archived .map file (zip archive) so we can fix the issue faster -->
 
 **Screenshots**
+
 <!-- Add screenshots to help explain your problem -->
 
 **System**
+
 <!-- Please add all the details. Verison is displayed as a part of the page title and also at loading screen. If the issue is for desktop version, please specify it as well -->
- - Version: ...
+
- - Browser: ...
+- Version: ...
- - OS: ...
+- Browser: ...
+- OS: ...

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,14 +1,14 @@
 ---
 name: Feature request
 about: Suggest an idea
-title: ''
+title: ""
 labels: pending review
 assignees: Azgaar
-
 ---
 
 <-- BEFORE CREATING PLEASE CHECK THE TO-DO LIST-->
 <-- https://trello.com/b/7x832DG4/fantasy-map-generator ->>
+
 **Problem**
 <-- Is your feature request related to a problem? Please describe. Ex.: I'm always frustrated when ... -->
 

.github/pull_request_template.md

@@ -1,23 +1,3 @@
 # Description
 
 <!-- Please include a summary of the change, motivation and context. It it's a but fix, add a reference in format #issue_number -->
-
-# Type of change
-
-<!-- Please put X into brackets of required option OR delete options that are not relevant -->
-
-- [ ] Bug fix
-- [ ] New feature
-- [ ] Refactoring / style
-- [ ] Documentation update / chore
-- [ ] Other (please describe)
-
-# Versioning
-
-<!-- Update the VERSION if you want the PR to be merged. Currently it's a manual 3-steps process:
-  * update VERSION in `versioning.js` using semver principle
-  * for all changed files update hash (the part after `?`) in place where file is requested (usually it's `index.html`)
-  * if the change can be really interesting for end-users, describe it inside the `showUpdateWindow()` function in `versioning.js` -->
-
-- [ ] Version is updated
-- [ ] Changed files hash is updated

public/modules/ui/options.js

@@ -1184,5 +1184,3 @@ function toggle3dOptions() {
     ThreeD.setResolution(this.value);
   }
 }
-
-// this is a test change