Use correct formatting for T.38 change note in UPGRADE.txt

git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.6.1@208503 65c4cc65-6c06-0410-ace0-fbb531ad65f3

diff --git a/UPGRADE.txt b/UPGRADE.txt
index 9a2901b4a07dc02a4ef95491c8fae6b71329b760..e804548f210b3cc54a764cc87af08daf1bf54f3d 100644 (file)
--- a/UPGRADE.txt
+++ b/UPGRADE.txt
@@ -20,15 +20,15 @@
 
 From 1.6.1.1 to 1.6.1.2:
 
-Beginning with this release, Asterisk's internal methods of
-negotiating T.38 (FAX over IP) sessions changed in
-non-backwards-compatible ways. Any applications that previously used
-AST_CONTROL_T38 control frames will have to be upgraded to use
-AST_CONTROL_T38_PARAMETERS control frames instead; app_fax.c is a good
-example of how to generate and respond to these frames. These changes
-were made to solve significant T.38 interoperability problems between
-Asterisk and various SIP/T.38 endpoints identified by many users of
-Asterisk.
+* Beginning with this release, Asterisk's internal methods of
+  negotiating T.38 (FAX over IP) sessions changed in
+  non-backwards-compatible ways. Any applications that previously used
+  AST_CONTROL_T38 control frames will have to be upgraded to use
+  AST_CONTROL_T38_PARAMETERS control frames instead; app_fax.c is a good
+  example of how to generate and respond to these frames. These changes
+  were made to solve significant T.38 interoperability problems between
+  Asterisk and various SIP/T.38 endpoints identified by many users of
+  Asterisk.
 
 From 1.6.0.1 to 1.6.1: