no more nexuiz on home page

[xonotic/xonotic.wiki.git] / Domination.md

diff --git a/Domination.md b/Domination.md
index ca0bc0a19030c2fc24677624aeb2f18deb4dcc1b..893a035336b1931d781b4e14305b5c3f1472cd42 100644 (file)
--- a/Domination.md
+++ b/Domination.md
@@ -4,7 +4,7 @@ Domination (DOM)
 Object of the Game
 ------------------
 
-In domination, the goal is to capture and hold all control points on the map. Domination is similar to [Onslaught](Onslaught) but capturing a control point is easier in Domination, and in Domination points are given for holding a control point, and there is no generator. Rarely are maps made exclusively for Domination, generally an existing [CTF](Capture_the_Flag) or [TDM](Team_Deathmatch) map receives Domination features.
+In domination, the goal is to capture and hold all control points on the map. Domination is similar to [Onslaught](Onslaught) but capturing a control point is easier in Domination, and in Domination points are given for holding a control point, and there is no generator. Rarely are maps made exclusively for Domination, generally an existing [CTF](Capture-the-Flag) or [TDM](Team-Deathmatch) map receives Domination features.
 
 Map Entities
 ------------
@@ -13,7 +13,7 @@ A domination map must have at the very least 4 entities.
 
 ### dom\_team
 
-dom\_team entites declare the teams available in the game and what models are shown when they take a control point. To create it, right click and go to "domination\>dom\_team". There must be at least 3 per map: Two teams and one empty team (for when the control point is not taken).
+dom\_team entites declare the teams available in the game and what models are shown when they take a control point. To create it, right click and go to “domination\>dom\_team”. There must be at least 3 per map: Two teams and one empty team (for when the control point is not taken).
 
     // entity 244
     {
@@ -44,7 +44,7 @@ dom\_team entites declare the teams available in the game and what models are sh
     "model" "models/domination/dom_unclaimed.md3"
     }
 
-These are the three dom\_team entites you must have on your map. It does not matter where they are placed. The first two examples here declare two dom teams: blue and red. The third declares the "empty team". It is best to copy these verbatim into your map, as their structure does not change (of course, the coordinates do change depending on where you placed them).
+These are the three dom\_team entites you must have on your map. It does not matter where they are placed. The first two examples here declare two dom teams: blue and red. The third declares the “empty team”. It is best to copy these verbatim into your map, as their structure does not change (of course, the coordinates do change depending on where you placed them).
 
 ### dom\_controlpoint
 
@@ -54,17 +54,17 @@ These are the actual control points that players will capture. They do not have
     "origin" "0.000000 2240.000000 608.000000"
     "message" " has captured ^1Red Base^3"
 
-The key here is the "message" field, which allows you to set the message shown when a controlpoint is captured. Generally, the format of this is " has captured CONTROLPOINTNAME". You can also use color codes in these messages, as shown in the above example.
+The key here is the “message” field, which allows you to set the message shown when a controlpoint is captured. Generally, the format of this is " has captured CONTROLPOINTNAME". You can also use color codes in these messages, as shown in the above example.
 
 Helpful Hints and Tips
 ----------------------
 
--   <Insert Hints Here>
+-   _(Insert Hints Here)_
 
 List of Demos and Videos
 ------------------------
 
--   Demo: <Insert Demo or Video Here>
--   Players: <Insert Player Names Here>
--   Key Points: <Insert key points in match here>
+-   Demo: _(Insert Demo or Video Here)_
+-   Players: _(Insert Player Names Here)_
+-   Key Points: _(Insert key points in match here)_