Basic Guidelines

Do not anthropomorphize. Do not imply that programs or hardware can think or feel. For example, avoid a message such as the following:
```
[node name] node does not speak any of our protocols
```
Instead, write a message such as:
```
Node [node name] cannot use Windows NT protocols
```

Avoid the word "Bad." Try to find a more descriptive term to tell the user what is wrong. For example, avoid, messages such as the following:

bad link          // Avoid!
bad size          // Avoid!
bad argument      // Avoid!
bad address       // Avoid!
bad CRC           // Avoid!

Use full sentences. For example, use "Binding is too long" instead of "Binding too long."
Place a searchable word at the start of each message. Avoid starting a message with an article. (the, a, or an). Never put a placeholder variable, such as %1 or %2, at the beginning of a message, since this makes it very difficult for a user to look up the message in our Help File. Instead, write the message so that a searchable word is at the beginning and the placeholder is embedded in the message. For example:
```
Log file %1 is full.
   NOT:  %1 log file is full.

Listen failed in %1.
   NOT:  %1: Listen failed. 

Computer name %1 is a domain controller of domain %2.
   NOT:  %1 is a domain controller of domain %2.
```