summaryrefslogtreecommitdiff
path: root/contributing
diff options
context:
space:
mode:
authorTanami <Tanami@web>2010-01-14 17:06:19 +0000
committerGNU Hurd web pages engine <web-hurd@gnu.org>2010-01-14 17:06:19 +0000
commit69d85e0708b1061676b009b462446a06df946cdc (patch)
treece17c060f8d73e833ee210996bed83d0d4322a61 /contributing
parentc5bc8d142e613f7fa4d9df084fe967ec1502540d (diff)
fixed various spelling and grammar issues
Diffstat (limited to 'contributing')
-rw-r--r--contributing/web_pages.mdwn36
1 files changed, 18 insertions, 18 deletions
diff --git a/contributing/web_pages.mdwn b/contributing/web_pages.mdwn
index e01a0040..390cb942 100644
--- a/contributing/web_pages.mdwn
+++ b/contributing/web_pages.mdwn
@@ -57,35 +57,35 @@ There are [[more detailed instructions about editing news items|news]].
</a>
When you commit changes, either using the web interface or checking them in
-into the repository, they'll not become visible on
-<http://www.gnu.org/software/hurd/> immediatelly, but first of all only on
+into the repository; they won't become visible on
+<http://www.gnu.org/software/hurd/> immediately, but on
<http://www.bddebian.com:8888/~hurd-web/> instead. The former set of pages,
the official GNU Hurd web appearance, will be updated periodically (but
-manually) from the latter one, where every edit is visible immediatelly. This
+manually) from the latter one, where every edit is visible immediately. This
is so that we have a chance to have the pages make fit for appearance on
`www.gnu.org`, but you are nevertheless able to work on all pages
unrestrictedly.
-# Edit Via the Web Interface
+# Editing via the Web Interface
-When you found a page you want to work on, just follow the *Edit* link on the
-top of the page. When doing this for the first time, this will first transfer
-you to a page where you have to create an account. After logging in, you
-can edit the pages.
+When you have found a page you want to work on, just follow the *Edit* link at the
+top of the page. When doing this for the first time, this will first redirect
+you to a page where you will have to create an account. After logging in, you
+can edit pages.
# Working on a Checkout of the Git Repository
-(!) What is being described here are only the basics. The checkouts are
+(!) What is being described here is only the basics. The checkouts are
completely valid Git repositories and can (and want to) be treated as such.
Consult the Git documentation about how to shuffle around with branches, how to
rename files, how to add arbitrary data files, and so on.
(!) Before attempting any bigger editing work (to which you are sincerely
-invited!) be sure to check the involved pages' *Discussion* subpages (linked
+invited!) be sure to check the involved pages' *Discussion* sub-pages (linked
from the pages' header line) and in there take down (short) notes about the
-editing endeavors you're going to undertake. Doing so should help to (a) avoid
+editing endeavours you're going to undertake. Doing so should help to (a) avoid
double work and (b) avoid merge conflicts if you install your changes into the
main repository.
@@ -105,24 +105,24 @@ identity:
## Getting the Sources
-For being able to do a checkout from which you can later directly push your
+To be able to do a checkout from which you can later directly push your
changes back into the master repository, you need a
[[shell_account_on_*flubber*|public_hurd_boxen]] and need to be a member of
-the *hurd-web* group. (It's also very much recommenable that you set up your local
-ssh configuration as advised on that page.) If you have an account on there:
+the *hurd-web* group. (It's also recommended that you set up your local
+SSH configuration as advised on that page.) If you have an account on there:
$ git clone flubber:~hurd-web/hurd-web [dest]
If you don't have such an account or don't have your login data handy, you can
-still get the pages the read-only way.
+still get pages the read-only way.
Note that this -- currently -- is not the data from the master server, but from
-a mirror of it, so it may be lacking behind a bit from time to time.
+a mirror of it, so it may be lagging behind a bit from time to time.
$ git clone git://git.savannah.gnu.org/hurd/web.git [dest]
If that also doesn't work out, you have yet another chance: pull over the HTTP
-protocol. Not very efficient (read: rather inefficient), but it works. This
+protocol. Not very efficient (read: rather inefficient), but it works. This
is also read-only.
$ git clone http://www.bddebian.com:8888/git/hurd-web [dest]
@@ -197,7 +197,7 @@ Or, to directly create a new page:
$ w3m 'file:///$LIB/ikiwiki-w3m.cgi/hurd-web.cgi?page=open_issues/gnumach_has_a_bug&do=create'
Note that the changes you do via `w3m` will not be committed to the VCS (see
-[[render_locally]] for details).
+[[render_locally]] for details.)
## Publish Your Changes