client: Unbreak standalone build

[empserver] / info / Overview.t

diff --git a/info/Overview.t b/info/Overview.t
index 265126d097b72a0ac4f8892d1ebb5d3be847b726..a9d07fe53b0d9abb05c788f2d1db76b86ce2f57a 100644 (file)
--- a/info/Overview.t
+++ b/info/Overview.t
@@ -90,7 +90,7 @@ unless you are very careful,
 it's probably not a good idea to rely on these automatics.
 .in
 .s1
-Bureaucratic Time Units (BTU's)
+Bureaucratic Time Units (BTUs)
 .in +0.3i
 .s1
 To prevent the more fanatical Empire players
@@ -103,31 +103,31 @@ You can't log in again until the counter resets itself
 (usually at midnight).
 .s1
 The other control on the number of commands that you may issue
-are called ``Bureaucratic Time Units'' or BTU's.
+are called ``Bureaucratic Time Units'' or BTUs.
 A BTU is an arbitrary amount of bureaucratic bookkeeping that
 your government must spend to perform a certain function.
-Most commands that are not merely informative cost BTU's.
+Most commands that are not merely informative cost BTUs.
 .s1
-BTU's are generated by your country's capital.
-The more efficient your capital, the more BTU's that are generated.
-The number of BTU's also depend on the game's settings.. See the 
+BTUs are generated by your country's capital.
+The more efficient your capital, the more BTUs that are generated.
+The number of BTUs also depend on the game's settings.. See the
 output of the 'version' command for an estimate of BTU generation speeds.
-However, you may have a maximum of 512 BTU's at any one time.
-And once your BTU's reach zero, you may not issue any commands
-that use BTU's.
+However, you may have a maximum of 512 BTUs at any one time.
+And once your BTUs reach zero, you may not issue any commands
+that use BTUs.
 .s1
-Three things to note about BTU's:
+Three things to note about BTUs:
 .in +\w'00)\0\0'u
 .s1
 .L 1)
-Since commands use up BTU's,
+Since commands use up BTUs,
 this limits the number of commands
 that a player may issue over a particular time period.
 This has the effect of preventing the Empire fanatic
 from overruning other players with less free time to log on.
 .s1
 .L 2)
-The build-up of BTU's is constant and does not depend on being
+The build-up of BTUs is constant and does not depend on being
 logged in.
 This allows players to participate when it is convenient rather
 than at some fixed time
@@ -163,7 +163,7 @@ Until you \*Qbreak sanctuary\*U,
 your country is effectively in stasis.
 Nothing will change until you actually log in and
 force a change
-(such as designating a capital to begin accumulating BTU's).
+(such as designating a capital to begin accumulating BTUs).
 .s1
 The absolutely minimal set of information pages you should read are:
 break, map, ann, wire, tel, read, expl, move, res, cen, dist, thresh, lev,
@@ -216,6 +216,7 @@ and partly on the Unix system at Davis Polk & Wardwell,
 by Peter Langston with invaluable goading from
 Joe Stetson, Robert Bradbury, Nat Howard, Brian Redman, Adam Buchsbaum,
 and a myriad of others.
+.s1
 Since Langston never released source code for his version,
 Dave Pare and friends de-compiled it in that same year and have
 created this version
@@ -226,9 +227,11 @@ code, most notably, Dave Pare added plane units in 1986, Jeff Bailey
 added many configurable options in the KSU distribution, Thomas
 Ruschak added land units and missions in 1992-1993 and released the
 "Chainsaw" server, and Ken Stevens rewrote much of the server code in
-1995 and released the "Empire2" server, and Steve McClure and the Wolfpack 
-made lots
-of other changes and released the "Empire4" server in August of 1996.
+1995 and released the "Empire 2" server.
+Steve McClure and the Wolfpack made lots
+of other changes and released "Empire 4" in August of 1996.
+The game is still maintained by the Wolfpack team.  Markus Armbruster
+serves as technical lead since 2004.
 .in
 .s1
 .SA "Novice, Expert, Introduction"