X-Git-Url: http://g0dil.de/git?a=blobdiff_plain;f=senf%2FSocket%2FFramingPolicy.hh;h=171f31ce4d93918b10929fcc77e74ebdd7f9bdbf;hb=0e87ffe1cd4de41a27a29c427d7538789e4e3a43;hp=5359c2710e5496e9fa918e2748202ca48473fc90;hpb=601d1f509f5bb24df167a4dd5a20da67a0af9af8;p=senf.git

diff --git a/senf/Socket/FramingPolicy.hh b/senf/Socket/FramingPolicy.hh
index 5359c27..171f31c 100644
--- a/senf/Socket/FramingPolicy.hh
+++ b/senf/Socket/FramingPolicy.hh
@@ -31,12 +31,12 @@
 #include "SocketPolicy.hh"
 
 //#include "FramingPolicy.mpp"
-///////////////////////////////hh.p////////////////////////////////////////
+//-/////////////////////////////////////////////////////////////////////////////////////////////////
 
 namespace senf {
 
     /// \addtogroup policy_impl_group
-    /// @{
+    //\{
 
     /** \brief FramingPolicy for stream oriented sockets
 
@@ -55,16 +55,16 @@ namespace senf {
         API. It however affects the semantics of the read and write
         operations. On a datagram socket, each read() or write() call
         we read or write a single datagram. Datagram boundaries are
-        kept intact accross the network.
+        kept intact across the network.
      */
     struct DatagramFramingPolicy : public FramingPolicyBase
     {};
 
-    /// @}
+    //\}
 
 }
 
-///////////////////////////////hh.e////////////////////////////////////////
+//-/////////////////////////////////////////////////////////////////////////////////////////////////
 //#include "FramingPolicy.cci"
 //#include "FramingPolicy.ct"
 //#include "FramingPolicy.cti"