Skip to content

Commit a0418dd

Browse files
Update README.md
1 parent 7a48f5f commit a0418dd

1 file changed

Lines changed: 6 additions & 3 deletions

File tree

README.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ generated page as the output.
6666
If ever you need a Google Docs
6767
or Microsoft Word
6868
version of this, simply copy the rendered
69-
markdown file of GitHub and paste it
69+
Markdown file of GitHub and paste it
7070
on Google Docs or Microsoft Word, the format
7171
will still be correct.
7272

@@ -75,7 +75,7 @@ As you can see, it's very practical.
7575
## How To
7676
In the same way you keep your pages and assets in one
7777
directory and subdirectories on the server, it is
78-
the same thing in GitHub Pages through a GitHub repository.
78+
the same thing on GitHub Pages through a GitHub repository.
7979

8080
For a user, `<username>.github.io` is the pattern by default
8181
so that GitHub Pages can build the site. Meaning, you should
@@ -113,7 +113,8 @@ just set the proper configuration in `Settings`.
113113
- `gh-pages` is a branch,
114114
to create this, go to `Branch`,
115115
type in the box 'gh-pages'
116-
then hit `Enter`.
116+
then click the pop up so that
117+
it will be created.
117118

118119
- `/docs` is a subfolder of the main `branch`,
119120
just click `Create new file` then type
@@ -176,6 +177,8 @@ on top of the HTML file.
176177
> 2. Create a repository or use an existing one.
177178
>
178179
> 3. Go to `Settings` and look for GitHub Pages.
180+
For free accounts, GitHub does not allow you
181+
to host from a private repo.
179182
>
180183
> 4. Select where GitHub Pages should build
181184
the pages, either from:

0 commit comments

Comments
 (0)