1 files changed, 11 insertions, 11 deletions
diff --git a/documentation/Fl_Multiline_Input.html b/documentation/Fl_Multiline_Input.html
index dfec9c12d..dd8c4ab16 100644
--- a/documentation/Fl_Multiline_Input.html
+++ b/documentation/Fl_Multiline_Input.html
@@ -17,13 +17,13 @@
 </PRE>
 </UL>
 <H3>Description</H3>
- This input field displays '\n' characters as new lines rather than ^J, 
-and accepts the Return, Tab, and up and down arrow keys.  This is for 
-editing multiline text. 
-<P>This is far from the nirvana of text editors, and is probably only 
-good for small bits of text, 10 lines at most.  I think FLTK can be 
-used to write a powerful text editor, but it is not going to be a 
-built-in feature.  Powerful text editors in a toolkit are a big source 
+ This input field displays '\n' characters as new lines rather than ^J,
+and accepts the Return, Tab, and up and down arrow keys.  This is for
+editing multiline text.
+<P>This is far from the nirvana of text editors, and is probably only
+good for small bits of text, 10 lines at most.  I think FLTK can be
+used to write a powerful text editor, but it is not going to be a
+built-in feature.  Powerful text editors in a toolkit are a big source
 of bloat. </P>
 <H3>Methods</H3>
 <UL>
@@ -33,11 +33,11 @@ of bloat. </P>
 </LI>
 </UL>
 <H4><A name=Fl_Multiline_Input.Fl_Multiline_Input>
-Fl_Multiline_Input::Fl_Multiline_Input(int x, int y, int w, int h, 
+Fl_Multiline_Input::Fl_Multiline_Input(int x, int y, int w, int h,
 const char *label = 0)</A></H4>
- Creates a new <TT>Fl_Multiline_Input</TT> widget using the given 
+ Creates a new <TT>Fl_Multiline_Input</TT> widget using the given
 position, size, and label string. The default boxtype is <TT>FL_DOWN_BOX</TT>
-. 
-<H4><A name=Fl_Multiline_Input.~Fl_Multiline_Input>virtual 
+.
+<H4><A name=Fl_Multiline_Input.~Fl_Multiline_Input>virtual
 Fl_Multiline_Input::~Fl_Multiline_Input()</A></H4>
  Destroys the widget and any value associated with it. </BODY></HTML>