X-Git-Url: https://code.citadel.org/?a=blobdiff_plain;f=citadel%2Ftechdoc%2Fhack.txt;fp=citadel%2Ftechdoc%2Fhack.txt;h=bbcb0acd7bfa6f14dcf47c62bb101185959ca98a;hb=d7d893c0cd64ca92ff93457094ec151d106342e9;hp=59c9fbf8dfe8d0c907045823f0027562027bbe72;hpb=c0a3e8894b0d554b73d404ea496a1836db6e0ed9;p=citadel.git

diff --git a/citadel/techdoc/hack.txt b/citadel/techdoc/hack.txt
index 59c9fbf8d..bbcb0acd7 100644
--- a/citadel/techdoc/hack.txt
+++ b/citadel/techdoc/hack.txt
@@ -1,5 +1,5 @@
             ------------------------------------------------------
-             The totally incomplete guide to Citadel/UX internals
+             The totally incomplete guide to Citadel internals
             ------------------------------------------------------
 
  Citadel has evolved quite a bit since its early days, and the data structures
@@ -280,7 +280,7 @@ T	Date/Time	A 32-bit integer containing the date and time of
                         the message in standard UNIX format (the number
                         of seconds since January 1, 1970 GMT).
 U       Subject         Optional.  Developers may choose whether they wish to
-                        generate or display subject fields.  Citadel/UX does
+                        generate or display subject fields.  Citadel does
                         not generate them, but it does print them when found.
 0	Error		This field is typically never found in a message on
 			disk or in transit.  Message scanning modules are
@@ -352,7 +352,7 @@ please see network.txt on its operation and functionality (if any).
 
 			Portability issues
  
- Citadel/UX is 64-bit clean, architecture-independent, and Year 2000
+ Citadel is 64-bit clean, architecture-independent, and Year 2000
 compliant.  The software should compile on any POSIX compliant system with
 a full pthreads implementation and TCP/IP support.  In the future we may
 try to port it to non-POSIX systems as well.