all .md files: Remove useless whitespaces from markdown files

Changes after executing the SpaceConsistency Bear. Closes coala#529
SerekKiri · Oct 25, 2018 · bd50ee6 · bd50ee6
1 parent 346464a
commit bd50ee6
Show file tree

Hide file tree

Showing 36 changed files with 161 additions and 154 deletions.
diff --git a/README.md b/README.md
@@ -30,7 +30,7 @@ Why?
 ## Usage
 
 To clone the repository and run this website on your local machine, [install Jekyll](https://jekyllrb.com/docs/installation/) for your OS and type the following commands:
-				
+
     $ sudo gem install jekyll bundler
     $ git clone https://github.com/coala/projects.git
     $ cd projects
@@ -54,7 +54,7 @@ A sample project definition is available [here](https://github.com/coala/project
 
 Users can also add FAQs by simply creating a markdown file in _faq folder.
 
-Format for faq markdown file is as follows: 
+Format for faq markdown file is as follows:
 ```
 ---
 Question: <Write the question here>

diff --git a/_faq/gsoc-requirements.md b/_faq/gsoc-requirements.md
@@ -5,5 +5,4 @@ Other than the [requirements from Google](https://developers.google.com/open-sou
 
 * You have completed the [coala Newcomers guide](https://coala.io/newcomer)
 * You have a submission to [our usability survey](https://coala.io/usability)
-	so we know that you know how to *use coala*.
-
+  so we know that you know how to *use coala*.
diff --git a/_faq/i-want-to-do-a-gsoc.md b/_faq/i-want-to-do-a-gsoc.md
@@ -1,5 +1,5 @@
 ---
 question: "I want to do a GSoC!"
 ---
-Great! This is the right place. Check out the other questions and 
+Great! This is the right place. Check out the other questions and
 most importantly the projects page.
diff --git a/_faq/is-mentor-necessary.md b/_faq/is-mentor-necessary.md
@@ -1,6 +1,6 @@
 ---
 question: "A showcased project on the website doesn't have a mentor, but
-	I'm interested in that project?"
+           I'm interested in that project?"
 ---
 You just have to choose a project and write an awesome proposal.
 Mentors are set after we choose the projects (which is done by choosing the students).

diff --git a/_faq/own-project-idea.md b/_faq/own-project-idea.md
@@ -1,5 +1,5 @@
 ---
 question: "I have an own project idea! (Mentors and students!)"
 ---
-Superb! We recommend you submit your idea to [our projects 
+Superb! We recommend you submit your idea to [our projects
 repository](https://github.com/coala/projects) as a pull request.
diff --git a/_faq/thesis.md b/_faq/thesis.md
@@ -4,7 +4,7 @@ question: "I want to write a thesis with coala!"
 Great! This is the right place. Check out the other questions and most
 importantly the projects page.
 If you have own ideas we recommend you submit them to our [projects
-repository](https://github.com/coala/projects) as a pull request 
-regardless if you want to do them yourself or not. 
+repository](https://github.com/coala/projects) as a pull request
+regardless if you want to do them yourself or not.
 You can find further information regarding thesis writing with coala
 [here](http://coala.io/thesis).
diff --git a/_layouts/report.md b/_layouts/report.md
@@ -22,7 +22,7 @@
                     <h4 class="left light">Google Summer of Code {{ page.date | date: '%Y' }} Work Product Submission </h4>
                 </div>
                 <br>
-            </div> 
+            </div>
             <br>
             <div class="row no-margin">
                 <div class="col m6">
@@ -107,7 +107,7 @@
                         </div>
                     </div>
                 </div>
-            </div>  
+            </div>
             <br>
              <div class="row no-margin">
                 <div class="col m12">
@@ -127,14 +127,14 @@
                     </thead>
                     <tbody class="card activity">
                         {% for commits in page.activity %}
-                        {% for c in commits %} 
+                        {% for c in commits %}
                            <tr>
                                 <td class="fl">{{ c[1][0]["repo"] | slice: 0 }}</td>
                                 <td class="">&nbsp;{{ c[1][0]["repo"] }}</td>
                                 <td><a href='{{ c[1][1]["link"] }}'>View</a></td>
                                 <td>{{ c[1][2]["details"] | markdownify}}</td>
                            </tr>
-                        {% endfor %}                      
+                        {% endfor %}
                         {% endfor %}
                     </tbody>
                 </table>
@@ -148,4 +148,4 @@
             <br><br>
         </div>
     </body>
-</html> 
+</html>
diff --git a/_projects/automate-dependency-repology.md b/_projects/automate-dependency-repology.md
@@ -37,8 +37,8 @@ installing these dependencies.
 
 Repology is a packaging hub. It analyzes a lot of package repositories and
 other sources, comparing packages versions across them and gatherinng relevant
-information. It shows you in which repositories a given project is packaged, 
-which version is the latest and which needs updating, who maintains the 
+information. It shows you in which repositories a given project is packaged,
+which version is the latest and which needs updating, who maintains the
 package, and other related information. The student has to use this information
 and implement improvments to the automated management of dependencies.
 
@@ -57,7 +57,7 @@ suitable scope and make a proposal accordingly.
 ##### CODING PHASE 1
 
 * All the existing LinterBears and Package Manager classes are connected with their respective Repology IDs.
-* Documentation added on how to do the same for new Linter Bears to 
+* Documentation added on how to do the same for new Linter Bears to
   [Writing Linter Bears](https://api.coala.io/en/latest/Developers/Writing_Linter_Bears.html)
 
 ##### CODING PHASE 2

diff --git a/_projects/bear-updates.md b/_projects/bear-updates.md
@@ -16,7 +16,7 @@ name: "Improve Lint Bear Quality"
 requirements:
   - "The participant should have one bugfix patch to any bear accepted."
   - "The participant should have understanding of the linter and test framework for bears."
-  - "The proposal should contain issues which are planned to be addressed, chosen 
+  - "The proposal should contain issues which are planned to be addressed, chosen
      (and potentially [filed](https://github.com/coala/coala-bears/issues/new)) by the student."
 status: disabled
 tags:
@@ -27,17 +27,17 @@ tags:
 
 This project is about improving the general quality of coala's linter bears.
 
-Since it is very easy to write them even for very inexperienced contributors, 
+Since it is very easy to write them even for very inexperienced contributors,
 linter bears in coala often suffer from mediocre quality, especially once they
 made it into the codebase.
 They do work, but not necessarily on all platforms or for all usecases. They are documented, but not
-necessarily understandable. They are tested, but lack corner cases or exploratory tests. 
+necessarily understandable. They are tested, but lack corner cases or exploratory tests.
 [See existing issues](https://github.com/coala/coala-bears/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%2Flintbears)
 
 Students working on this project familiarize themselves in-depth with the
 working of the `linter` decorator and the existing linter bears. They identify
 systematic issues with the way linter bears are developed and maintained and
-work to fix those issues and improve and amend 
+work to fix those issues and improve and amend
 [existing documentation](http://api.coala.io/en/latest/Developers/Writing_Linter_Bears.html)
 to avoid them in the future. A number of existing bears is updated and improved to fit the new standards.
 
@@ -48,7 +48,7 @@ Possible areas to investigate include:
   cumbersome and ugly to add more test cases.
 * Support for underlying tool: The support for the underlying tool is mostly
   left to the contributers discretion. Students could come up with a guideline
-  on how well a tool's options must be supported and documented or even 
+  on how well a tool's options must be supported and documented or even
   automated ways to test for this (maybe via a bear?).
 
 #### Milestones
@@ -61,9 +61,9 @@ Possible areas to investigate include:
 
 ##### CODING PHASE 1
 
- * Ideas for how to solve each of the identified issues are drafted. 
+ * Ideas for how to solve each of the identified issues are drafted.
    If possible ways to automatically check bears are drafted.
- * Changes to the [linter bear documentation](http://api.coala.io/en/latest/Developers/Writing_Linter_Bears.html) 
+ * Changes to the [linter bear documentation](http://api.coala.io/en/latest/Developers/Writing_Linter_Bears.html)
    to improve quality of future bears are proposed.
  * A list of bears which suffer from any of the identified issues is composed.
 

diff --git a/_projects/coala-cli.md b/_projects/coala-cli.md
@@ -148,5 +148,5 @@ https://github.com/coala/coala/issues/2912
 https://github.com/coala/coala/issues/2699
 https://github.com/coala/coala/issues/2541
 
-GSoC Proposal for this project:- 
+GSoC Proposal for this project:-
 https://docs.google.com/document/d/10FHYhRzK9IxroDoPxI5V_nWCR3DO-g-C-g12B0WKkQA/edit?usp=sharing
diff --git a/_projects/coala-web.md b/_projects/coala-web.md
@@ -41,12 +41,12 @@ tags:
 
 This project aims to increase the user base of coala and provide a web based
 interface to use coala on their projects. The project is conceptually built upon
-various previous projects (coala-gui, coala-html) which have helped us refine, 
+various previous projects (coala-gui, coala-html) which have helped us refine,
 redefine and revisit our GUI approach.
 
 By providing first time users a one click interface to obtain a coafile online
 and to run coala at coala.io on their projects by two means, by pasting the code
-in the given editor box, and by pasting the link to their GitHub repository in 
+in the given editor box, and by pasting the link to their GitHub repository in
 a link box. This will help them to get started with coala very easily.
 
 The next thing where the project will help us is that it will provide an
@@ -67,7 +67,7 @@ bot name in the issues section of their GitHub repositories, and then this bot
 will comment back with a coafile for their project. Additionaly it will also
 make a Pull Request with that coafile. The prototype can be found
 [here](https://github.com/hemangsk/gh-node-bot-prototype) and an example issue
-is [here](https://github.com/rahulcode22/Hackerrank/issues/6). 
+is [here](https://github.com/rahulcode22/Hackerrank/issues/6).
 
 #### Milestones
 
@@ -97,6 +97,6 @@ from coala-html.
 
 * Add CI on landing-frontend, projects and webServices.
 * Enhance coala-html UI and Add searching and filtering functionality.
-* Solve [coala-html#34](https://github.com/coala/coala-html/issues/34) and 
+* Solve [coala-html#34](https://github.com/coala/coala-html/issues/34) and
 [coala-html#33](https://github.com/coala/coala-html/issues/33)
 * Revisit code in landing-frontend, projects and webServices and add tests.
diff --git a/_projects/create-jenkins-plugin.md b/_projects/create-jenkins-plugin.md
@@ -25,7 +25,7 @@ tags:
 ---
 
 **Disabled: This project is not available for GSOC 2018. See Jenkin's GSOC
-[page](https://summerofcode.withgoogle.com/organizations/5572716199936000/) 
+[page](https://summerofcode.withgoogle.com/organizations/5572716199936000/)
 if you are interested in working with them**
 
 Jenkins is the most popular ci-cd server, and there are many corporations

diff --git a/_projects/documentation-extraction.md b/_projects/documentation-extraction.md
@@ -28,7 +28,7 @@ end up having one.
 
 This probably is partly due to the fact that having a second place to write
 documentation makes it easy to "forget" about it. To solve this problem, and
-also to offer developers easier access to some important information, many 
+also to offer developers easier access to some important information, many
 languages support having documentation in source files. The problem with this
 is, that most linters only work on code or pure documentation files but can not
 lint documentation in source files. This leads to a lack of checks for in

diff --git a/_projects/enhance-coala-quickstart.md b/_projects/enhance-coala-quickstart.md
@@ -51,9 +51,9 @@ However, there’s scope for improvement in the following areas:
   files are to be linted with csslint, we could use this information to target
   CSSLintBear at exactly these files.
 - Improving the interface:
-	- Removing non user-friendly warnings.
-	- Increasing automation.
-	- Validate user input before writing to the generated coafile.
+    - Removing non user-friendly warnings.
+    - Increasing automation.
+    - Validate user input before writing to the generated coafile.
 - Continuous Integration: Like other coala repositories, add Appveyor
   (Windows) and Travis (OSX) integartions.