Skip to content

Commit bd50ee6

Browse files
committed
all .md files: Remove useless whitespaces from markdown files
Changes after executing the SpaceConsistency Bear. Closes #529
1 parent 346464a commit bd50ee6

36 files changed

+161
-154
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Why?
3030
## Usage
3131

3232
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:
33-
33+
3434
$ sudo gem install jekyll bundler
3535
$ git clone https://github.com/coala/projects.git
3636
$ cd projects
@@ -54,7 +54,7 @@ A sample project definition is available [here](https://github.com/coala/project
5454

5555
Users can also add FAQs by simply creating a markdown file in _faq folder.
5656

57-
Format for faq markdown file is as follows:
57+
Format for faq markdown file is as follows:
5858
```
5959
---
6060
Question: <Write the question here>

_faq/gsoc-requirements.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,5 +5,4 @@ Other than the [requirements from Google](https://developers.google.com/open-sou
55

66
* You have completed the [coala Newcomers guide](https://coala.io/newcomer)
77
* You have a submission to [our usability survey](https://coala.io/usability)
8-
so we know that you know how to *use coala*.
9-
8+
so we know that you know how to *use coala*.

_faq/i-want-to-do-a-gsoc.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
22
question: "I want to do a GSoC!"
33
---
4-
Great! This is the right place. Check out the other questions and
4+
Great! This is the right place. Check out the other questions and
55
most importantly the projects page.

_faq/is-mentor-necessary.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
question: "A showcased project on the website doesn't have a mentor, but
3-
I'm interested in that project?"
3+
I'm interested in that project?"
44
---
55
You just have to choose a project and write an awesome proposal.
66
Mentors are set after we choose the projects (which is done by choosing the students).

_faq/own-project-idea.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
22
question: "I have an own project idea! (Mentors and students!)"
33
---
4-
Superb! We recommend you submit your idea to [our projects
4+
Superb! We recommend you submit your idea to [our projects
55
repository](https://github.com/coala/projects) as a pull request.

_faq/thesis.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ question: "I want to write a thesis with coala!"
44
Great! This is the right place. Check out the other questions and most
55
importantly the projects page.
66
If you have own ideas we recommend you submit them to our [projects
7-
repository](https://github.com/coala/projects) as a pull request
8-
regardless if you want to do them yourself or not.
7+
repository](https://github.com/coala/projects) as a pull request
8+
regardless if you want to do them yourself or not.
99
You can find further information regarding thesis writing with coala
1010
[here](http://coala.io/thesis).

_layouts/report.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@
2222
<h4 class="left light">Google Summer of Code {{ page.date | date: '%Y' }} Work Product Submission </h4>
2323
</div>
2424
<br>
25-
</div>
25+
</div>
2626
<br>
2727
<div class="row no-margin">
2828
<div class="col m6">
@@ -107,7 +107,7 @@
107107
</div>
108108
</div>
109109
</div>
110-
</div>
110+
</div>
111111
<br>
112112
<div class="row no-margin">
113113
<div class="col m12">
@@ -127,14 +127,14 @@
127127
</thead>
128128
<tbody class="card activity">
129129
{% for commits in page.activity %}
130-
{% for c in commits %}
130+
{% for c in commits %}
131131
<tr>
132132
<td class="fl">{{ c[1][0]["repo"] | slice: 0 }}</td>
133133
<td class="">&nbsp;{{ c[1][0]["repo"] }}</td>
134134
<td><a href='{{ c[1][1]["link"] }}'>View</a></td>
135135
<td>{{ c[1][2]["details"] | markdownify}}</td>
136136
</tr>
137-
{% endfor %}
137+
{% endfor %}
138138
{% endfor %}
139139
</tbody>
140140
</table>
@@ -148,4 +148,4 @@
148148
<br><br>
149149
</div>
150150
</body>
151-
</html>
151+
</html>

_projects/automate-dependency-repology.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,8 @@ installing these dependencies.
3737

3838
Repology is a packaging hub. It analyzes a lot of package repositories and
3939
other sources, comparing packages versions across them and gatherinng relevant
40-
information. It shows you in which repositories a given project is packaged,
41-
which version is the latest and which needs updating, who maintains the
40+
information. It shows you in which repositories a given project is packaged,
41+
which version is the latest and which needs updating, who maintains the
4242
package, and other related information. The student has to use this information
4343
and implement improvments to the automated management of dependencies.
4444

@@ -57,7 +57,7 @@ suitable scope and make a proposal accordingly.
5757
##### CODING PHASE 1
5858

5959
* All the existing LinterBears and Package Manager classes are connected with their respective Repology IDs.
60-
* Documentation added on how to do the same for new Linter Bears to
60+
* Documentation added on how to do the same for new Linter Bears to
6161
[Writing Linter Bears](https://api.coala.io/en/latest/Developers/Writing_Linter_Bears.html)
6262

6363
##### CODING PHASE 2

_projects/bear-updates.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ name: "Improve Lint Bear Quality"
1616
requirements:
1717
- "The participant should have one bugfix patch to any bear accepted."
1818
- "The participant should have understanding of the linter and test framework for bears."
19-
- "The proposal should contain issues which are planned to be addressed, chosen
19+
- "The proposal should contain issues which are planned to be addressed, chosen
2020
(and potentially [filed](https://github.com/coala/coala-bears/issues/new)) by the student."
2121
status: disabled
2222
tags:
@@ -27,17 +27,17 @@ tags:
2727

2828
This project is about improving the general quality of coala's linter bears.
2929

30-
Since it is very easy to write them even for very inexperienced contributors,
30+
Since it is very easy to write them even for very inexperienced contributors,
3131
linter bears in coala often suffer from mediocre quality, especially once they
3232
made it into the codebase.
3333
They do work, but not necessarily on all platforms or for all usecases. They are documented, but not
34-
necessarily understandable. They are tested, but lack corner cases or exploratory tests.
34+
necessarily understandable. They are tested, but lack corner cases or exploratory tests.
3535
[See existing issues](https://github.com/coala/coala-bears/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%2Flintbears)
3636

3737
Students working on this project familiarize themselves in-depth with the
3838
working of the `linter` decorator and the existing linter bears. They identify
3939
systematic issues with the way linter bears are developed and maintained and
40-
work to fix those issues and improve and amend
40+
work to fix those issues and improve and amend
4141
[existing documentation](http://api.coala.io/en/latest/Developers/Writing_Linter_Bears.html)
4242
to avoid them in the future. A number of existing bears is updated and improved to fit the new standards.
4343

@@ -48,7 +48,7 @@ Possible areas to investigate include:
4848
cumbersome and ugly to add more test cases.
4949
* Support for underlying tool: The support for the underlying tool is mostly
5050
left to the contributers discretion. Students could come up with a guideline
51-
on how well a tool's options must be supported and documented or even
51+
on how well a tool's options must be supported and documented or even
5252
automated ways to test for this (maybe via a bear?).
5353

5454
#### Milestones
@@ -61,9 +61,9 @@ Possible areas to investigate include:
6161

6262
##### CODING PHASE 1
6363

64-
* Ideas for how to solve each of the identified issues are drafted.
64+
* Ideas for how to solve each of the identified issues are drafted.
6565
If possible ways to automatically check bears are drafted.
66-
* Changes to the [linter bear documentation](http://api.coala.io/en/latest/Developers/Writing_Linter_Bears.html)
66+
* Changes to the [linter bear documentation](http://api.coala.io/en/latest/Developers/Writing_Linter_Bears.html)
6767
to improve quality of future bears are proposed.
6868
* A list of bears which suffer from any of the identified issues is composed.
6969

_projects/coala-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -148,5 +148,5 @@ https://github.com/coala/coala/issues/2912
148148
https://github.com/coala/coala/issues/2699
149149
https://github.com/coala/coala/issues/2541
150150

151-
GSoC Proposal for this project:-
151+
GSoC Proposal for this project:-
152152
https://docs.google.com/document/d/10FHYhRzK9IxroDoPxI5V_nWCR3DO-g-C-g12B0WKkQA/edit?usp=sharing

0 commit comments

Comments
 (0)