Fix sports_info -> sport_info in the man page.

Remove the GameInfo TODO, it's completed.

diff --git a/doc/TODO b/doc/TODO
index f63cbe759ce5e62242c16c792075a06afdea9c61..efcaf0bcac186690dcd5731a01e15349b1053090 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -13,7 +13,6 @@
      * AutoRaceResultsXML
      * jfilexml
      * Schedule_Changes_XML
      * AutoRaceResultsXML
      * jfilexml
      * Schedule_Changes_XML

-     * GameInfoXML

      * SportInfoListing
 
 5. Try mass import of Auto_Racing_Schedule_XML.
      * SportInfoListing
 
 5. Try mass import of Auto_Racing_Schedule_XML.

diff --git a/doc/man1/htsn-import.1 b/doc/man1/htsn-import.1
index d31634f45ff24e350b1aad4f17a5f0e2f88d7432..c9ac457f4c3e4414e325052d6c9f686867f8b16a 100644 (file)
--- a/doc/man1/htsn-import.1
+++ b/doc/man1/htsn-import.1
@@ -106,9 +106,9 @@ recapxml.dtd
 WorldBaseballPreviewXML.dtd
 .RE
 .P
 WorldBaseballPreviewXML.dtd
 .RE
 .P

-The GameInfo and SportsInfo types do not have their own top-level
+The GameInfo and SportInfo types do not have their own top-level

 tables in the database. Instead, their raw XML is stored in either the
 tables in the database. Instead, their raw XML is stored in either the

-\(dqgame_info\(dq or \(dqsports_info\(dq table respectively.
+\(dqgame_info\(dq or \(dqsport_info\(dq table respectively.

 
 .SH DATABASE SCHEMA
 .P
 
 .SH DATABASE SCHEMA
 .P


@@ -153,11 +153,11 @@ unique constraint in the top-level table's \(dqxml_file_id\(dq will
 prevent duplication in this case anyway.
 .P
 The aforementioned exceptions are the \(dqgame_info\(dq and
 prevent duplication in this case anyway.
 .P
 The aforementioned exceptions are the \(dqgame_info\(dq and

-\(dqsports_info\(dq tables. These tables contain the raw XML for a
+\(dqsport_info\(dq tables. These tables contain the raw XML for a

 number of DTDs that are not handled individually. This is partially
 for backwards-compatibility with a legacy implementation, but is
 mostly a stopgap due to a lack of resources at the moment. These two
 number of DTDs that are not handled individually. This is partially
 for backwards-compatibility with a legacy implementation, but is
 mostly a stopgap due to a lack of resources at the moment. These two

-tables (game_info and sports_info) still possess timestamps that allow
+tables (game_info and sport_info) still possess timestamps that allow

 us to prune old data.
 .P
 UML diagrams of the resulting database schema for each XML document
 us to prune old data.
 .P
 UML diagrams of the resulting database schema for each XML document