From 428ff9d1f83d870f5542cad7c583564e5b98b3ff Mon Sep 17 00:00:00 2001 From: dl267 Date: Tue, 27 Apr 2004 09:59:03 +0200 Subject: [PATCH] [svn r5851] Corrected some spelling errors --- handbook/known.htm | 2 +- handbook/rescue.htm | 6 +++--- handbook/stool.htm | 2 +- handbook/update.htm | 23 +++++++++++++---------- 4 files changed, 18 insertions(+), 15 deletions(-) diff --git a/handbook/known.htm b/handbook/known.htm index 0439071db..9dbbbd87e 100644 --- a/handbook/known.htm +++ b/handbook/known.htm @@ -17,7 +17,7 @@ not since 1999, certainly not since 2001). Do not rely on it!

CUCC #1623/info
28 -red painted omega Marking in Stogerweg near laserpoint +red painted omega Marking in Stogerweg near laser point denotes nearby entrance
31 diff --git a/handbook/rescue.htm b/handbook/rescue.htm index 08e9fd9f3..834bdf92c 100644 --- a/handbook/rescue.htm +++ b/handbook/rescue.htm @@ -229,7 +229,7 @@ rescue kit (see section 3.5.1), with the aims of:

The others should follow behind carrying the equipment listed in section 3.5.2 and a bag of hauling gear (section 3.5.4). They should cave carefully and preserve -their energy as far as possible, as it may be a long resue. Their main aim is +their energy as far as possible, as it may be a long rescue. Their main aim is to prevent the deterioration of the victim. Their secondary aim is to start getting the victim(s) out of the cave, if they have sufficient personnel.

@@ -287,7 +287,7 @@ href="#s354">3.5.4) if there is any chance of it being needed.

Meanwhile, the Austrian rescue authorities should be alerted. Ask the BergRestaurant (if it is open) or the Loser Hütte to radio for help, or phone directly if a working -mobile phone and german speaker are on hand. Failing this, contact base +mobile phone and German speaker are on hand. Failing this, contact base camp and get them to alert the rescue services. However, there will probably be a delay of at least 4 hours before they reach the cave (longer if it is dark). Do as much as you can in this time. A German speaker is almost @@ -614,7 +614,7 @@ pressing. part of the patient's body. Start at the head and work down to the toes. Talk to the patient. All along the exam make sure he can feel your hands. See if he can grip you hands firmly and equally. You are looking for -additional wounds, swellings, eccymosis (black marks from pooling blood), +additional wounds, swellings, ecchymosis (black marks from pooling blood), tenderness, etc. Always do this survey. Write down the results.

  • When you have worked out what is wrong, write down the results. You diff --git a/handbook/stool.htm b/handbook/stool.htm index 50af07509..1cd9f5638 100644 --- a/handbook/stool.htm +++ b/handbook/stool.htm @@ -36,7 +36,7 @@ to keep the smell down.

    • minging it down with rain. On a hot day the smell will be keen, and disease rife.

    -

  • DO take good aim! The best spots (i.e. relatively comfy, not to far away, and good'n'deep) will be discovered and used by several people. No-one wnats to see or smell yesterday's slop streaked down the side of an otherwise good grike.

    • +

  • DO take good aim! The best spots (i.e. relatively comfy, not to far away, and good'n'deep) will be discovered and used by several people. No-one wants to see or smell yesterday's slop streaked down the side of an otherwise good grike.

  • DO think about where your offerings may be washed during a rain-storm – into Steinbrückenhöhle perhaps?

    • diff --git a/handbook/update.htm b/handbook/update.htm index 320e74799..d3f30fb4a 100644 --- a/handbook/update.htm +++ b/handbook/update.htm @@ -11,7 +11,7 @@

    Rationale for having a system at all:

    -

    For years, the website has been built by hand-editing html pages, +

    For years, the website has been built by hand-editing HTML pages, "traditionally" by one or two people, in constant email contact. Obviously those people were thoroughly familiar with the locations of all the pages, the conventions used for naming files, the style used throughout the site and @@ -69,7 +69,7 @@ can "check out" a copy of the page they want to change. They then make the changes or additions required, and "commit" the new page back into the system. The system keeps a record of all such changes, with a log message in which you should say why the change was made (the system knows who you -are and when you commited the change, so you don't need to tell it that).

    +are and when you committed the change, so you don't need to tell it that).

    In order to join in the work, the central CVS repository needs to know about you, so it can allow you to commit changes into the system (and thus @@ -81,20 +81,20 @@ site, or whatever).

    Software requirements

    You need a system which has a CVS client and supports SSH, so that you can -log in without sending a password in clear text over the internet. You need +log in without sending a password in clear text over the Internet. You need an editor with which you are happy to edit web pages. Ideally this will NOT be one of the commercial WYSIWYG web editors which add whole loads of guff to your webpage in a manner that you don't see (and which, incidentally, makes the pages vastly harder to maintain for the next person who comes -along with a basic html editor, not to mention making the pages load more +along with a basic HTML editor, not to mention making the pages load more slowly and typically work in fewer browsers). Most of us use basic -text editors with extensions that make editing html easier. The easiest +text editors with extensions that make editing HTML easier. The easiest way to get all this is to have a Linux machine, since most distributions have all the tools you need ready built in. The rest of this page assumes that you are doing all this on a recent Linux system. There are a few useful links for those using Mac, RISC OS or Windows machines along with the links to more detailed documentation at the end of -this page. The cvs machine itself is a Linux box, and some of the +this page. The CVS machine itself is a Linux box, and some of the commands you need to use involve typing at the command line on that machine, so some familiarity with Unix/Linux will make you feel more at home.

    @@ -127,7 +127,7 @@ With recent versions of openssh, you need to type

    ssh-keygen -t dsa
    -

    doeswith older versions, you may find that "-t" is not a valid option, in +

    while with older versions, you may find that "-t" is not a valid option, in which case

    ssh-keygen -d
    @@ -169,7 +169,7 @@ commands on your own machine, so get out of that command line with

    exit

    To use the CVS commands on your local machine (for checking out pages -to edit and commiting them back) you need to tell cvs where the archive +to edit and committing them back) you need to tell cvs where the archive is. You can include a "-d username@cvs.cucc.survex.com:/export/cvs" with cvs commands (useful if you use cvs on more than one repository), but it is usually easier to add

    @@ -196,7 +196,7 @@ cvs checkout expoweb

    and then move into the directory tree to make your changes. Thus far, everything has been at the command line, but often doing the editing will be more convenient through a desktop interface. You might find that -you want to set your file browser *not* to display an html view of the +you want to set your file browser *not* to display an HTML view of the files, otherwise you will end up browsing the pages, rather than the file tree, which makes editing much harder :-(

    @@ -311,7 +311,7 @@ a "?" are ones which cvs doesn't know about - maybe you haven't "cvs add"ed them yet.

    Updating the website

    -

    Having commited any changes to the cvs tree, connect to cvs.cucc.survex.com +

    Having committed any changes to the cvs tree, connect to cvs.cucc.survex.com via ssh and run the command /opt/expo/bin/www-update. (You can do this all in one step by just typing ssh cvs.cucc.survex.com /opt/expo/bin/www-update.)

    @@ -364,6 +364,9 @@ info is actually stored and served up.

    journals. Complicated by expo articles being in a separate hierarchy.
  • Translations
  • Other people's work - the noinfo hierarchy.
    • +
  • Style guide for writing cave descriptions: correct use of boldface +(once for each passage name, at the primary definition thereof; other +uses of the name should be links to this, and certainly should not be bold.)