docs/motorRecord.html: Document HOMF and HOMR better

Modern motion controller may have more advanced homing sequences
the what is specified in the motorRecord documentation.
However, many installations and implementations still use the
HOMF and HOMR fields to initiate such a homing sequence.
Make this more clear.

docs/motorRecord.html

@@ -2377,7 +2377,13 @@ <h2>Field Descriptions</h2> In addition to fields common to all record types (se
     motor stops, the VAL field will be set equal to the RBV field, and the DVAL 
     field will be set equal to the DRBV field.&nbsp; These fields can be set to 1, 
     but setting either field to 0 results in an error.&nbsp; The record sets HOM[F/R] 
-    to zero when the homing procedure is either completed or aborted.</td>
+    to zero when the homing procedure is either completed or aborted.
+    Note that modern controllers, depending on their firmware and configuration,
+    may do different things. Examples are home into the limit switch, move
+    into a limit switch, return and search for a home switch or other sequences.
+    Often HOMF and HOMR then yield the same functionality. 
+    And the controller may choose to do nothing, if a motor is not homable.
+</td>
   </tr>
   <tr valign="top">
     <td><br>