info/Empire4.4: Improve a few change log entries

[empserver] / info / lost.t

diff --git a/info/lost.t b/info/lost.t
index 8a186db455ee4a1b58706ab62012889cf74cd1b5..541a54d264284501f3e1bda1af4f4d73e78b9511 100644 (file)
--- a/info/lost.t
+++ b/info/lost.t
@@ -7,9 +7,9 @@ database for your country.
 .s1
 All lost items are timestamped at the time they were lost.  If
 you had a previously lost item in the database, and then build a
-new item of the same type with the same id, or regain an item of the
+new item of the same type with the same ID, or regain an item of the
 same type with the same
-id, it is removed from the database.  This is done because the new item
+ID, it is removed from the database.  This is done because the new item
 will now show up in the other dump commands, and is no longer lost.
 .s1
 Lost items are kept in the database for 48 hours (default) but may
@@ -18,7 +18,7 @@ command does not remove items from the database.  That is where the
 timestamp functionality becomes important.
 .s1
 While the lost command does not take any arguments, it does
-take the standard syntax for selecting information.  
+take the standard syntax for selecting information.
 (see \*Qinfo Selector\*U).
 .s1
 A typical usage might be:
@@ -48,7 +48,7 @@ The type of lost item.  They are as follows:
     4 - Nuclear stockpile
 .L id
 The # of the ship, plane, land unit or nuke.  All of these items
-are identified by id.  Sectors are identified by x and y.
+are identified by ID.  Sectors are identified by x and y.
 .L x
 The x coordinate of the lost item when it was lost.
 .L y
@@ -57,4 +57,4 @@ The y coordinate of the lost item when it was lost.
 The timestamp of when the item was lost.
 .in
 .s1
-.SA "xdump, dump, ldump, sdump, ndump, pdump, Ships, Planes, LandUnits, Sectors, Clients"
+.SA "xdump, dump, ldump, sdump, ndump, pdump, Ships, Planes, Nukes, LandUnits, Sectors"