Skip to content

Commit e73ce03

Browse files
committed
Replace github by GitHub
This is how the GitHub people render the name.
1 parent 88f9b26 commit e73ce03

File tree

1 file changed

+11
-10
lines changed

1 file changed

+11
-10
lines changed

lib/Language/modules.pod

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -13,15 +13,16 @@ directory|http://modules.perl6.org>. C<:)>
1313
For now, the process requires that you use git for your module's version
1414
control.
1515
16-
The instructions herein require that you have a github account so that
17-
your module can be shared from its github repository.
16+
The instructions herein require that you have a
17+
L<GitHub|http://www.github.com> account so that your module can be shared
18+
from its GitHub repository.
1819
1920
To share your module then, do the following:
2021
2122
=item Create a project directory named after your module. For
2223
example, if your module is Vortex::TotalPerspective, then create a
2324
project directory named C<Vortex-TotalPerspective>. This project
24-
directory name will also be used as the github repo name.
25+
directory name will also be used as the GitHub repo name.
2526
2627
=begin item
2728
Make your project directory look like this:
@@ -48,7 +49,7 @@ To share your module then, do the following:
4849
=end item
4950
5051
=item The C<README.md> file is a markdown-formatted text file, which
51-
will later be automatically rendered as html by github.
52+
will later be automatically rendered as HTML by GitHub.
5253
5354
=item Regarding the C<LICENSE> file, if you have no other preference,
5455
you might just use the same one that Rakudo Perl 6 uses. Just
@@ -99,13 +100,13 @@ To share your module then, do the following:
99100
=item Put your project under git version control if you haven't done so
100101
already.
101102
102-
=item Once you're happy with your project, create a repo for it at github.
103-
See L<github's help docs|https://help.github.com/> if necessary. Your
104-
github repo should be named the same as your project directory. Immediately
105-
after creating the github repo, github shows you how to configure your
106-
local repo to know about your github repo.
103+
=item Once you're happy with your project, create a repo for it at GitHub.
104+
See L<GitHub's help docs|https://help.github.com/> if necessary. Your
105+
GitHub repo should be named the same as your project directory. Immediately
106+
after creating the GitHub repo, GitHub shows you how to configure your
107+
local repo to know about your GitHub repo.
107108
108-
=item Push your project to github.
109+
=item Push your project to GitHub.
109110
110111
=item Ping someone on IRC (#perl6 at freenode) to either show you how to
111112
add your module to the L<ecosystem|https://github.com/perl6/ecosystem>, or

0 commit comments

Comments
 (0)