Minor doc touch-ups and typo fixes

diff --git a/docs/confreg/callforpapers.md b/docs/confreg/callforpapers.md
index f8091ef90e0094816ceea249db6e5ca5f9de4709..45e53229f8f81f351b8c0e09b798360975f7db39 100644 (file)
--- a/docs/confreg/callforpapers.md
+++ b/docs/confreg/callforpapers.md
@@ -13,7 +13,7 @@ introductory text (if you want one), and decide if you want to ask for
 skill levels.
 
 If you want to ask for Tracks in the call for papers, make sure you
-[create them](schedule#tracks) create them first, and flag them as "in
+[create them](schedule#tracks) first, and flag them as "in
 cfp". If no tracks with "in cfp" set exists, the track field will
 automatically be excluded from the call for papers form.
 
@@ -36,7 +36,7 @@ colleagues. However, those rules are not in any way enforced in the
 system, but are handled manually by the people on the committee.
 
 Each voter can leave a comment for each talk in the text field, and
-view each others comment. All voting is open to all members of the
+view each others comments. All voting is open to all members of the
 committee.
 
 Click the talk title to view full details about the talk.

diff --git a/docs/confreg/registrations.md b/docs/confreg/registrations.md
index 1d0ef183abe575978c3c882d0c112a12dd14b319..a63d1116b4e65f388383b22e7641307f9ecabcc5 100644 (file)
--- a/docs/confreg/registrations.md
+++ b/docs/confreg/registrations.md
@@ -12,7 +12,7 @@ succeeds can always be discussed..):
    a community account, or one can be created as part of the signup
    process.
 1. The exact fields to be filled out can be
-   [configured](configuring) configured at the conference level, for
+   [configured](configuring) at the conference level, for
    example if there should be a field about t-shirt size or not.
 1. The attendee can incrementally fill out and save in between if
    necessary. If they do that, they will at regular intervals receive
@@ -92,7 +92,7 @@ The system for bulk payments is automatically disabled once the
 ## Registration types and classes <a name="typesandclasses"></a>
 
 When making a registration, the attendee picks the appropriate
-[registration type}(#regtypes). There always has to be at least one registration
+[registration type](#regtypes). There always has to be at least one registration
 type, even for the most simple conference.
 
 A registration type contains the different kinds of parameters that are per-type