minor changes and typo corrections in migration_1_3.dox

git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@6797 ea41ed52-d2ee-0310-a9c1-e6b18d33e121

1 files changed, 6 insertions, 6 deletions

diff --git a/documentation/src/migration_1_3.dox b/documentation/src/migration_1_3.dox
index b28c18e6b..4c1f1bfba 100644
--- a/documentation/src/migration_1_3.dox
+++ b/documentation/src/migration_1_3.dox
@@ -15,7 +15,7 @@ then you should first consult Appendix \ref migration_1_1.
 
 Fl_Scroll::scroll_to(int x, int y) replaces Fl_Scroll::position(int x, int y).
 
-This change was needed, because Fl_Scroll::position(int,int) redefined
+This change was needed because Fl_Scroll::position(int,int) redefined
 Fl_Widget::position(int,int), but with a completely different function (moving
 the scrollbars instead of moving the widget).
 
@@ -24,26 +24,26 @@ Fl_Scroll-derived widgets, if you used Fl_Scroll::position(int x, int y)
 to position <b>the scrollbars</b> (not the widget itself).
 
 The compiler will not detect any errors, because your calls to 
-\b \e position(int x, int y) will be calling Fl_Widget::position(int x, int y).
+\b position(int x, int y) will be calling Fl_Widget::position(int x, int y).
 
 
-\section migration_1_3_unicode Unicode (utf-8)
+\section migration_1_3_unicode Unicode (UTF-8)
 
-FLTK 1.3 uses Unicode (utf-8) encoding internally. If you are only using
+FLTK 1.3 uses Unicode (UTF-8) encoding internally. If you are only using
 characters in the ASCII range (32-127), there is a high probability that
 you don't need to modify your code. However, if you use international
 characters (128-255), encoded as e.g. Windows codepage 1252, ISO-8859-1,
 ISO-8859-15 or any other encoding, then you will need to update your character
 string constants and widget input data accordingly.
 
+Please refer to the \ref unicode chapter for more details.
+
 \note It is important that, although your software uses only ASCII characters
 for input to FLTK widgets, the user may enter non-ASCII characters, and FLTK
 will return these characters with utf-8 encoding to your application, e.g.
 via Fl_Input::value(). You \b will need to re-encode them to \b your (non-utf-8)
 encoding, otherwise you might see or print garbage in your data.
 
-\link unicode For more information see here.\endlink
-
 
 \section migration_1_3_int_coords Widget Coordinate Representation