fix: text on audio pipeline wwas messed up

emiago · emiago · commit 55ca49ad06a0 · 2025-08-13T14:59:55.000+02:00
diff --git a/docs/audio_pipelines/index.html b/docs/audio_pipelines/index.html
@@ -14,9 +14,9 @@
   <title>Audio Pipelines – Diago</title>
   <meta name="description" content="Everything is io.Reader and io.Writer
 Diago follows GO std lib and providing interface for Reader/Writer when it comes reading and writing media. This made easier usage of RTP framework and optimizations, by providing end user standard library io.Reader io.Writer to pass his media.
-In other words creating reader or writer pipelines allows to build interceptors, encoders, decoders without introducing overhead of contention and buffer reusage.
+In other words creating reader or writer pipelines allows to build interceptors, encoders, decoders without introducing overhead of contention and buffer reuse.
 media and audio package also provide all this helpers for making audio pipelines straightforward. In realtime media streaming, audio is sampled at constant rate.
-Some of io operations you encounter have helpers media package like media.Copy , media.ReadAll, which are better suited intead std io" />
+Some of io operations you encounter have helpers media package like media.Copy , media.ReadAll, which are better suited instead std io" />
 
   
     <link rel="canonical" href="https://emiago.github.io/diago/docs/audio_pipelines/" itemprop="url" />
@@ -28,10 +28,10 @@
 <meta property="og:description" content="Everything is io.Reader and io.Writer
 Diago follows GO std lib and providing interface for Reader/Writer when it comes reading and writing media.
 This made easier usage of RTP framework and optimizations, by providing end user standard library io.Reader io.Writer to pass his media.
-In other words creating reader or writer pipelines allows to build interceptors, encoders, decoders without introducing overhead of contention and buffer reusage.
+In other words creating reader or writer pipelines allows to build interceptors, encoders, decoders without introducing overhead of contention and buffer reuse.
 media and audio package also provide all this helpers for making audio pipelines straightforward.
 In realtime media  streaming, audio is sampled at constant rate.
-Some of io operations you encounter have helpers media package like media.Copy , media.ReadAll, which are better suited intead std io" />
+Some of io operations you encounter have helpers media package like media.Copy , media.ReadAll, which are better suited instead std io" />
 <meta property="og:type" content="article" />
 <meta property="og:url" content="https://emiago.github.io/diago/docs/audio_pipelines/" /><meta property="article:section" content="docs" />
 
@@ -41,17 +41,17 @@
   <meta itemprop="name" content="Audio Pipelines">
   <meta itemprop="description" content="Everything is io.Reader and io.Writer
 Diago follows GO std lib and providing interface for Reader/Writer when it comes reading and writing media. This made easier usage of RTP framework and optimizations, by providing end user standard library io.Reader io.Writer to pass his media.
-In other words creating reader or writer pipelines allows to build interceptors, encoders, decoders without introducing overhead of contention and buffer reusage.
+In other words creating reader or writer pipelines allows to build interceptors, encoders, decoders without introducing overhead of contention and buffer reuse.
 media and audio package also provide all this helpers for making audio pipelines straightforward. In realtime media streaming, audio is sampled at constant rate.
-Some of io operations you encounter have helpers media package like media.Copy , media.ReadAll, which are better suited intead std io">
-  <meta itemprop="wordCount" content="189">
+Some of io operations you encounter have helpers media package like media.Copy , media.ReadAll, which are better suited instead std io">
+  <meta itemprop="wordCount" content="190">
   <meta name="twitter:card" content="summary">
   <meta name="twitter:title" content="Audio Pipelines">
   <meta name="twitter:description" content="Everything is io.Reader and io.Writer
 Diago follows GO std lib and providing interface for Reader/Writer when it comes reading and writing media. This made easier usage of RTP framework and optimizations, by providing end user standard library io.Reader io.Writer to pass his media.
-In other words creating reader or writer pipelines allows to build interceptors, encoders, decoders without introducing overhead of contention and buffer reusage.
+In other words creating reader or writer pipelines allows to build interceptors, encoders, decoders without introducing overhead of contention and buffer reuse.
 media and audio package also provide all this helpers for making audio pipelines straightforward. In realtime media streaming, audio is sampled at constant rate.
-Some of io operations you encounter have helpers media package like media.Copy , media.ReadAll, which are better suited intead std io">
+Some of io operations you encounter have helpers media package like media.Copy , media.ReadAll, which are better suited instead std io">
 
     <link rel="preload" href="/diago/css/compiled/main.min.23a12191daf50c320fcb5ce50e8c895a47f37ce361f66be7c771e19f254b32b2.css" as="style" integrity="sha256-I6Ehkdr1DDIPy1zlDoyJWkfzfONh9mvnx3HhnyVLMrI=" />
     <link href="/diago/css/compiled/main.min.23a12191daf50c320fcb5ce50e8c895a47f37ce361f66be7c771e19f254b32b2.css" rel="stylesheet" integrity="sha256-I6Ehkdr1DDIPy1zlDoyJWkfzfONh9mvnx3HhnyVLMrI=" />
@@ -429,12 +429,12 @@ <h1>Audio Pipelines</h1>
           <p>Everything is io.Reader and io.Writer</p>
 <p>Diago follows GO std lib and providing interface for Reader/Writer when it comes reading and writing media.
 This made easier usage of RTP framework and optimizations, by providing end user standard library io.Reader io.Writer to pass his media.</p>
-<p>In other words creating reader or writer <strong>pipelines</strong> allows to build interceptors, encoders, decoders without introducing overhead of contention and buffer reusage.</p>
+<p>In other words creating reader or writer <strong>pipelines</strong> allows to build interceptors, encoders, decoders without introducing overhead of contention and buffer reuse.</p>
 <p><code>media</code> and <code>audio</code> package also provide all this helpers for making audio pipelines straightforward.
 In <strong>realtime media</strong>  streaming, audio is sampled at constant rate.<br>
-Some of io operations you encounter have helpers <code>media</code> package like <code>media.Copy</code> , <code>media.ReadAll</code>, which are better suited intead std <code>io</code></p>
+Some of io operations you encounter have helpers <code>media</code> package like <code>media.Copy</code> , <code>media.ReadAll</code>, which are better suited instead std <code>io</code></p>
 <h3>Creating Echo<span class="hx-absolute -hx-mt-20" id="creating-echo"></span>
-    <a href="#creating-echo" class="subheading-anchor" aria-label="Permalink for this section"></a></h3><p>Everything mostly begins by getting actuall <code>AudioReader</code> and <code>AudioWriter</code> from Dialog Session.</p>
+    <a href="#creating-echo" class="subheading-anchor" aria-label="Permalink for this section"></a></h3><p>Everything mostly begins by getting actual <code>AudioReader</code> and <code>AudioWriter</code> from Dialog Session.</p>
 <div class="hextra-code-block hx-relative hx-mt-6 first:hx-mt-0 hx-group/code">
   
 
@@ -468,9 +468,9 @@ <h3>Creating Echo<span class="hx-absolute -hx-mt-20" id="creating-echo"></span>
 
   
 </div>
-<p>For less memory alloc, better option is <code>media.CopyWithBuf</code> where controling buffer reusage can be made.</p>
+<p>For less memory alloc, better option is <code>media.CopyWithBuf</code> where controlling buffer reuse can be made.</p>
 <h3>More audio processing<span class="hx-absolute -hx-mt-20" id="more-audio-processing"></span>
-    <a href="#more-audio-processing" class="subheading-anchor" aria-label="Permalink for this section"></a></h3><p>For more <strong>audio</strong> processing <code>audio</code> like ex <strong>transcoding</strong> package provides you with prebuilt helpers for pipelining
+    <a href="#more-audio-processing" class="subheading-anchor" aria-label="Permalink for this section"></a></h3><p>For more <strong>audio</strong> processing <code>audio</code> (ex <strong>transcoding</strong>, <strong>wav streaming</strong>) package provides you with prebuilt helpers for pipelining
 More you can find here <a href="https://pkg.go.dev/github.com/emiago/diago/audio" target="_blank" rel="noopener">https://pkg.go.dev/github.com/emiago/diago/audio</a></p>
 
         </div>
diff --git a/docs/index.html b/docs/index.html
@@ -36,7 +36,7 @@
 Developing this kind of services can be challenging when it needs more behavior: monitoring, media control, integrations, databases etc…
 Diago with GO offers faster way of developing and testing communication services, but keeping care on providing low latency.
 More on Why Diago">
-  <meta itemprop="wordCount" content="266">
+  <meta itemprop="wordCount" content="261">
   <meta name="twitter:card" content="summary">
   <meta name="twitter:title" content="Diago">
   <meta name="twitter:description" content="Welcome to diago documentation!.
@@ -451,15 +451,14 @@ <h2>Core (Roadmap):<span class="hx-absolute -hx-mt-20" id="core-roadmap"></span>
 <li><input checked="" disabled="" type="checkbox"> Handling Reinvites with media updates</li>
 <li><input checked="" disabled="" type="checkbox"> Bridging as proxy media for 2 parties B2BUA</li>
 <li><input checked="" disabled="" type="checkbox"> Opus codec support</li>
-<li><input checked="" disabled="" type="checkbox"> Late Offer/Answer (Invite without SDP)</li>
 <li><input checked="" disabled="" type="checkbox"> Handling blind transfers (Refers)</li>
 <li><input disabled="" type="checkbox"> Handling attended transfers</li>
 <li><input disabled="" type="checkbox"> Handle Anonymous Trust Domain PAI handling (rfc3325) <strong>Partially Done</strong></li>
 <li><input disabled="" type="checkbox"> Conferencing audio</li>
 <li><input disabled="" type="checkbox"> DTMF with SIP INFO (Needed more in case webrtc)</li>
 <li><input disabled="" type="checkbox"> Writing Unit Test on Server with SIP and Media Recorder</li>
 <li><input disabled="" type="checkbox"> RTP symetric</li>
-<li><input checked="" disabled="" type="checkbox"> SRTP for more critical services</li>
+<li><input disabled="" type="checkbox"> SRTP for more critical services</li>
 <li><input checked="" disabled="" type="checkbox"> Simple Wav Stereo recording</li>
 <li><input disabled="" type="checkbox"> Webrtc as media stack (integration with pion) <strong>Experimental</strong></li>
 <li><input disabled="" type="checkbox"> Full IPV6 support (sipgo work) <strong>Supported but has corner cases</strong></li>
diff --git a/docs/index.xml b/docs/index.xml
@@ -509,12 +509,12 @@ If needed it will be exposed more as special thing.&lt;/p&gt;
         &lt;p&gt;Everything is io.Reader and io.Writer&lt;/p&gt;
 &lt;p&gt;Diago follows GO std lib and providing interface for Reader/Writer when it comes reading and writing media.
 This made easier usage of RTP framework and optimizations, by providing end user standard library io.Reader io.Writer to pass his media.&lt;/p&gt;
-&lt;p&gt;In other words creating reader or writer &lt;strong&gt;pipelines&lt;/strong&gt; allows to build interceptors, encoders, decoders without introducing overhead of contention and buffer reusage.&lt;/p&gt;
+&lt;p&gt;In other words creating reader or writer &lt;strong&gt;pipelines&lt;/strong&gt; allows to build interceptors, encoders, decoders without introducing overhead of contention and buffer reuse.&lt;/p&gt;
 &lt;p&gt;&lt;code&gt;media&lt;/code&gt; and &lt;code&gt;audio&lt;/code&gt; package also provide all this helpers for making audio pipelines straightforward.
 In &lt;strong&gt;realtime media&lt;/strong&gt;  streaming, audio is sampled at constant rate.&lt;br&gt;
-Some of io operations you encounter have helpers &lt;code&gt;media&lt;/code&gt; package like &lt;code&gt;media.Copy&lt;/code&gt; , &lt;code&gt;media.ReadAll&lt;/code&gt;, which are better suited intead std &lt;code&gt;io&lt;/code&gt;&lt;/p&gt;
+Some of io operations you encounter have helpers &lt;code&gt;media&lt;/code&gt; package like &lt;code&gt;media.Copy&lt;/code&gt; , &lt;code&gt;media.ReadAll&lt;/code&gt;, which are better suited instead std &lt;code&gt;io&lt;/code&gt;&lt;/p&gt;
 &lt;h3&gt;Creating Echo&lt;span class=&#34;hx-absolute -hx-mt-20&#34; id=&#34;creating-echo&#34;&gt;&lt;/span&gt;
-    &lt;a href=&#34;#creating-echo&#34; class=&#34;subheading-anchor&#34; aria-label=&#34;Permalink for this section&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;Everything mostly begins by getting actuall &lt;code&gt;AudioReader&lt;/code&gt; and &lt;code&gt;AudioWriter&lt;/code&gt; from Dialog Session.&lt;/p&gt;
+    &lt;a href=&#34;#creating-echo&#34; class=&#34;subheading-anchor&#34; aria-label=&#34;Permalink for this section&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;Everything mostly begins by getting actual &lt;code&gt;AudioReader&lt;/code&gt; and &lt;code&gt;AudioWriter&lt;/code&gt; from Dialog Session.&lt;/p&gt;
 &lt;div class=&#34;hextra-code-block hx-relative hx-mt-6 first:hx-mt-0 hx-group/code&#34;&gt;
   
 
@@ -548,9 +548,9 @@ Some of io operations you encounter have helpers &lt;code&gt;media&lt;/code&gt;
 
   
 &lt;/div&gt;
-&lt;p&gt;For less memory alloc, better option is &lt;code&gt;media.CopyWithBuf&lt;/code&gt; where controling buffer reusage can be made.&lt;/p&gt;
+&lt;p&gt;For less memory alloc, better option is &lt;code&gt;media.CopyWithBuf&lt;/code&gt; where controlling buffer reuse can be made.&lt;/p&gt;
 &lt;h3&gt;More audio processing&lt;span class=&#34;hx-absolute -hx-mt-20&#34; id=&#34;more-audio-processing&#34;&gt;&lt;/span&gt;
-    &lt;a href=&#34;#more-audio-processing&#34; class=&#34;subheading-anchor&#34; aria-label=&#34;Permalink for this section&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;For more &lt;strong&gt;audio&lt;/strong&gt; processing &lt;code&gt;audio&lt;/code&gt; like ex &lt;strong&gt;transcoding&lt;/strong&gt; package provides you with prebuilt helpers for pipelining
+    &lt;a href=&#34;#more-audio-processing&#34; class=&#34;subheading-anchor&#34; aria-label=&#34;Permalink for this section&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;For more &lt;strong&gt;audio&lt;/strong&gt; processing &lt;code&gt;audio&lt;/code&gt; (ex &lt;strong&gt;transcoding&lt;/strong&gt;, &lt;strong&gt;wav streaming&lt;/strong&gt;) package provides you with prebuilt helpers for pipelining
 More you can find here &lt;a href=&#34;https://pkg.go.dev/github.com/emiago/diago/audio&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;https://pkg.go.dev/github.com/emiago/diago/audio&lt;/a&gt;&lt;/p&gt;
 
       </description>
diff --git a/en.search-data.json b/en.search-data.json
