use inline defined hints

1 files changed, 13 insertions, 4 deletions

diff --git a/USE.md b/USE.md
index 59f8d2e..c13048d 100644
--- a/USE.md
+++ b/USE.md
@@ -1,12 +1,21 @@
 # Calendaring introduction
 
-Anyone can read calendars shared publicly at {{organisation}}.
+Anyone can read calendars shared publicly at Example orga.
 
 Your personal [[account]] grants read-only access to closed-group shared calendars.
 
 Custom group accounts provide write access to (closed-group or public) shared calendars.
 
 
+## Special strings
+
+NB! This documentation uses special strings
+which you may want to adapt for your local setup:
+
+organisation: Example orga
+eventhost: event.example.org
+
+
 ## Clients
 
 Recommended calendaring client depends on the operating system you use:
@@ -23,7 +32,7 @@ When you only need to read a calendar,
 the best (most efficient) is to subscribe to an **iCal** calender:
 
  1. Copy address of relevant calendar from web page
-    <http://{{eventhost}}/>.
+    <http://event.example.org/>.
  2. Open calendaring client, and add new account profile of type "ical".
  3. Paste the calendar address as server address.
 
@@ -37,14 +46,14 @@ To both read a calendar and help maintain its content,
 you need to setup a **CalDAV** profile:
 
  1. Open calendaring client, and add new account profile of type "CalDAV".
- 2. Server address: **{{eventhost}}:8443**
+ 2. Server address: **event.example.org:8443**
  3. Username and password: Either personal or calendar-group account credentials.
 
 If above fails, or if you want to specifically pick a single calender,
 use this alternative approach:
 
  1. Copy address of relevant calendar from web page
-    **https://{{eventhost}}:8443/calendars/users/USERNAME/**  
+    **https://event.example.org:8443/calendars/users/USERNAME/**  
     (replace USERNAME with either personal or calendar-group account name)
  2. Open calendaring client, and add new account profile of type "CalDAV".
  3. Paste the calendar address as server address.