X-Git-Url: https://git.pterodactylus.net/?a=blobdiff_plain;f=readme.txt;h=4ac04fc9677194dd0d115dbebc0905353a165144;hb=cd75427de26fc2ebc9baad558b1c0a081faa3b43;hp=3df7b4b4988996ba27c8488ac343e03e0b69b81f;hpb=023b2219068d481cd6a300982427c99bacd88a12;p=fms.git

diff --git a/readme.txt b/readme.txt
index 3df7b4b..4ac04fc 100644
--- a/readme.txt
+++ b/readme.txt
@@ -42,13 +42,14 @@ startup type in the service properties.
 If you are experiencing a problem with FMS that you can't solve, and you've
 already rebooted your machine, restarted FMS, and have reproduced the problem
 with a brand new database, follow these instructions.  Set the logging option
-to trace and restart FMS.  Create a post on the fms group that contains the
-operating system you are using, along with a description of the problem, what
-you have tried already, if you are using a precompiled binary, the startup
-lines from the log file as well as the portion that corresponds to the problem
-you are experiencing, and any other information you have that pertains to the
-problem.  Make sure to anonymize any IP addresses, host names, subnet masks,
-and keys from the log that you don't want people to know about.
+to trace and restart FMS.  Create a post on the fms group with a descriptive
+subject and a body that contains the operating system you are using, along with
+a description of the problem, what you have tried already, if you are using a
+precompiled binary, the startup lines from the log file as well as the portion
+that corresponds to the problem you are experiencing, and any other information
+you have that pertains to the problem.  Make sure to anonymize any IP addresses,
+host names, subnet masks, and keys from the log that you don't want people to
+know about.
 
 EXITING
 -------