summaryrefslogtreecommitdiffstats
path: root/edit.md
diff options
context:
space:
mode:
authorAmin Bandali <bandali@gnu.org>2020-07-26 10:10:30 -0400
committerAmin Bandali <bandali@gnu.org>2020-07-26 10:10:30 -0400
commit777062601439f74ad72a260964098d21bb73ff93 (patch)
tree3c18385b0240896ef3c2751a9d4b20a69b17738d /edit.md
parent161676e7cf95adc1dfc4c6207d344a4af18965ad (diff)
downloademacsconf-wiki-777062601439f74ad72a260964098d21bb73ff93.tar.xz
emacsconf-wiki-777062601439f74ad72a260964098d21bb73ff93.zip
edit: a few small tweaks
Diffstat (limited to 'edit.md')
-rw-r--r--edit.md19
1 files changed, 12 insertions, 7 deletions
diff --git a/edit.md b/edit.md
index 23069fd..e0a56ca 100644
--- a/edit.md
+++ b/edit.md
@@ -32,8 +32,9 @@ pushes), and avoiding `git://` (no transport security) and `https://`
To use the `ssh://` method, you need `openssh` installed on your
machine, which is available on virtually all GNU/Linux distributions
-and other Unix-like operating systems like the BSDs. You also need to
-download the ssh private key
+and other Unix-like operating systems like the BSDs.
+
+You also need to download the ssh private key
[`id_rsa_anon_git_emacsconf`](/id_rsa_anon_git_emacsconf) and install
it into `~/.ssh/` (the `.ssh` directory in your home directory). The
key fingerprint is `SHA256:XbUoLgO2YH9+phNPKvwq8w0Q/8NhaKfS/VE6pDwTPsM
@@ -77,8 +78,8 @@ one already) and add the following to it:
IdentityFile ~/.ssh/id_rsa_anon_git_emacsconf
The `Port 22` line is optional, since SSH uses port 22 by default.
-However, the SSH server listens on ports 21, 22, 53, 81, 8000, and
-8080 for your convenience if you need it.
+The SSH server listens on ports 21, 22, 53, 81, 8000, and 8080 for
+your convenience, if you need it.
You're now all set and ready to clone the repository containing the
wiki sources. To do so, run:
@@ -98,6 +99,10 @@ repository you just cloned. When you're done, do:
where `X`, `Y`, and `Z` are the files you changed; and `descriptive
commit message` is, well, a descriptive text describing your
-changes. :-) When you are ready, push your changes by running `git
-push`, and if all goes well, your commit should be pushed and your
-changes appear on the website within a few seconds.
+changes. :-)
+
+When you are ready, and assuming you have read and agree with the
+license terms linked at the top of this page, you can push your
+changes by running `git push`. If all goes well, your commit will be
+pushed, and your changes will appear on the website within a few
+seconds.