1 files changed, 19 insertions, 19 deletions

diff --git a/MediaBrowser.Model/Dlna/DlnaFlags.cs b/MediaBrowser.Model/Dlna/DlnaFlags.cs
index b981e8455c..d076e73ece 100644
--- a/MediaBrowser.Model/Dlna/DlnaFlags.cs
+++ b/MediaBrowser.Model/Dlna/DlnaFlags.cs
@@ -1,18 +1,18 @@
-using System;
+using System;
 
 namespace MediaBrowser.Model.Dlna
 {
     [Flags]
     public enum DlnaFlags : ulong
     {
-        /*!	<i>Background</i> transfer mode.
-		For use with upload and download transfers to and from the server. 
-		The primary difference between \ref DH_TransferMode_Interactive and 
-		\ref DH_TransferMode_Bulk is that the latter assumes that the user 
-		is not relying on the transfer for immediately rendering the content 
-		and there are no issues with causing a buffer overflow if the 
-		receiver uses TCP flow control to reduce total throughput.
-	    */
+        /*! <i>Background</i> transfer mode.
+            For use with upload and download transfers to and from the server.
+            The primary difference between \ref DH_TransferMode_Interactive and
+            \ref DH_TransferMode_Bulk is that the latter assumes that the user
+            is not relying on the transfer for immediately rendering the content
+            and there are no issues with causing a buffer overflow if the
+            receiver uses TCP flow control to reduce total throughput.
+        */
         BackgroundTransferMode = 1 << 22,
 
         ByteBasedSeek = 1 << 29,
@@ -21,10 +21,10 @@ namespace MediaBrowser.Model.Dlna
         DlnaV15 = 1 << 20,
 
         /*! <i>Interactive</i> transfer mode.
-            For best effort transfer of images and non-real-time transfers. 
-            URIs with image content usually support \ref DH_TransferMode_Bulk too. 
-            The primary difference between \ref DH_TransferMode_Interactive and 
-            \ref DH_TransferMode_Bulk is that the former assumes that the 
+            For best effort transfer of images and non-real-time transfers.
+            URIs with image content usually support \ref DH_TransferMode_Bulk too.
+            The primary difference between \ref DH_TransferMode_Interactive and
+            \ref DH_TransferMode_Bulk is that the former assumes that the
             transfer is intended for immediate rendering.
         */
         InteractiveTransferMode = 1 << 23,
@@ -35,14 +35,14 @@ namespace MediaBrowser.Model.Dlna
         SenderPaced = 1L << 31,
         SnIncrease = 1 << 26,
 
-        /*!	<i>Streaming</i> transfer mode.
-        The server transmits at a throughput sufficient for real-time playback of 
-        audio or video. URIs with audio or video often support the 
-        \ref DH_TransferMode_Interactive and \ref DH_TransferMode_Bulk transfer modes. 
-        The most well-known exception to this general claim is for live streams.
+        /*! <i>Streaming</i> transfer mode.
+            The server transmits at a throughput sufficient for real-time playback of
+            audio or video. URIs with audio or video often support the
+            \ref DH_TransferMode_Interactive and \ref DH_TransferMode_Bulk transfer modes.
+            The most well-known exception to this general claim is for live streams.
         */
         StreamingTransferMode = 1 << 24,
 
         TimeBasedSeek = 1 << 30
     }
-}
\ No newline at end of file
+}