Skip to content

Commit a3f23e4

Browse files
committed
fixup markdown
1 parent 5dfcbd2 commit a3f23e4

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ You can check if git support pcre by using the '-P' option
3333

3434
## Cloning repositories
3535

36-
You should start forking the main (metacpan-grep-front-end repository)[https://github.com/metacpan/metacpan-grep-front-end]
36+
You should start forking the main [metacpan-grep-front-end repository](https://github.com/metacpan/metacpan-grep-front-end)
3737
You can then clone it locally (where you should replace ~YOUR-GITHUB-USERNAME~ by your github username )
3838

3939
> git clone [email protected]:~YOUR-GITHUB-USERNAME~/metacpan-grep-front-end.git
@@ -42,10 +42,10 @@ You can then clone it locally (where you should replace ~YOUR-GITHUB-USERNAME~ b
4242

4343
The frontend is not using a database, but a `git repo` itself as a backend.
4444
For this the production is using one huge git repository (~20 Go) indexing all the CPAN in one place !
45-
You can read more on this topic and find tools used to build this Git repo on the (GitHub Repos)[https://grep.metacpan.org/source-code] page.
45+
You can read more on this topic and find tools used to build this Git repo on the [GitHub Repos](https://grep.metacpan.org/source-code) page.
4646

4747
We do not want to use such a beast during development cycles, we only need a smaller version of it,
48-
you can simply clone it from this (metacpan-cpan-extracted-lite)[https://github.com/metacpan/metacpan-cpan-extracted-lite].
48+
you can simply clone it from this [metacpan-cpan-extracted-lite](https://github.com/metacpan/metacpan-cpan-extracted-lite).
4949
It should be clone at the same level of *metacpan-grep-front-end* itself (do not clone it inside the repository).
5050

5151
# clone at the same level of metacpan-grep-front-end
@@ -121,7 +121,7 @@ From there you should be ready to
121121

122122
The project comes with a basic `.travis.yml` file.
123123

124-
If you want to start smoking your own branches, you simply need to link your [GitHub account](https://github.com)
125-
to your (Travis CI account)[https://travis-ci.org/], then enable the repository in your (Travis Dashboard)[https://travis-ci.org/dashboard]
124+
If you want to start smoking your own branches, you simply need to link your [GitHub account](https://github.com/)
125+
to your [Travis CI account](https://travis-ci.org/), then enable the repository in your [Travis Dashboard](https://travis-ci.org/dashboard)
126126

127127
Note that any Pull Request submitted via GitHub would trigger a Travis smoke without any settings required from your side :-)

0 commit comments

Comments
 (0)