Update RTMP_NOTES

RTMP_NOTES

@@ -1,24 +1,28 @@
 NOTES:
 
-1. Two new supplied media types for setMedia "rtmpa" and "rtmpv" - specify for rtmp audio streams and rtmp video streams. Example Audio:
-	 		jPlayer("setMedia", {
-            rtmpa: "rtmp://cpcode.edgefcs.net/ondemand/mp3:/path_to_my_audio/some_audio_track.mp3"
-	Example Video:
-			jPlayer("setMedia", {
-            rtmpv: "rtmp://cpcode.edgefcs.net/ondemand/mp4:/path_to_my_audio/some_audio_track.mp4"
+1. Two new supplied media types for setMedia "rtmpa" and "rtmpv" - specify for rtmp audio streams and rtmp video streams.
+
+Example Audio:
+	jPlayer("setMedia", {
+        rtmpa: "rtmp://cpcode.edgefcs.net/ondemand/mp3:/path_to_my_audio/some_audio_track.mp3"
+
+Example Video:
+	jPlayer("setMedia", {
+        rtmpv: "rtmp://cpcode.edgefcs.net/ondemand/mp4:/path_to_my_audio/some_audio_track.mp4"
 
 2. URL parsing of RTMP sources (which may need to be customized per usage, or extended/modified based on implementation needs) is located in the new ActionScript class files: JplayerRTMP.as - the relevant function is: parseRTMPsrcConnect(string) - this is where you should make accomodations for your FMS instance name, media location path, etc. Currently has basic support for parsing vod and live, but you may need to adjust this function to handle and parse your RTMP source URLs appropriately. Examples for splitting the host, appname and streamname are there, but if you have custom instances, or other needs, this is the place to edit/adjust.
 
 3. The changes to jquery.jplayer.js are very minor, the majority of the big changes are in the Jplayer.as to allow for the new RTMP formats "rtmpa" and "rtmpv" and to import a new JplayerRTMP.as and a ConnectManager class which add the bulk of the RTMP support.
 
 10/21/2011 UPDATE:
 
-	Video is now functioning properly. Several bug fixes related to video over rtmp are now in place allowing it to function as expected.
-	Optimized the buffering settings to provide a dual-threshold buffering approach for recorded/ondemand RTMP streams, and standard non dual-threshold buffering for LIVE content where technically there may not be anything to buffer.
+Video is now functioning properly. Several bug fixes related to video over rtmp are now in place allowing it to function as expected.
+Optimized the buffering settings to provide a dual-threshold buffering approach for recorded/ondemand RTMP streams, and standard non dual-threshold buffering for LIVE content where technically there may not be anything to buffer.
 
 08/11/2011 UPDATE:
-	Reworked the parseRTMPsrcConnect to add significant amount of intelligence about rtmp sources. Now as long as its a valid rtmp source, it will be parsed appropriately. I also added in support for instance name detection without the much slower practice of multiple connection attempts to try and figure out the instance name verus portion of the stream name. Use a single "^" instead of a "/" directly after the instance name in your rtmp source url as a sentinel to indicate the end of a custom instance name after an FMS appname. Example:
-		rtmp://media.somehost.com:1935/someAppName/customInstanceName^mp3:thepathtosomefolder/folder/my_great_audio.mp3
+
+Reworked the parseRTMPsrcConnect to add significant amount of intelligence about rtmp sources. Now as long as its a valid rtmp source, it will be parsed appropriately. I also added in support for instance name detection without the much slower practice of multiple connection attempts to try and figure out the instance name verus portion of the stream name. Use a single "^" instead of a "/" directly after the instance name in your rtmp source url as a sentinel to indicate the end of a custom instance name after an FMS appname. Example:
+rtmp://media.somehost.com:1935/someAppName/customInstanceName^mp3:thepathtosomefolder/folder/my_great_audio.mp3
 
 TODO Future Features List: