deploy: 077785c

print.html

@@ -584,7 +584,7 @@ <h2 id="reserved-namespaces"><a class="header" href="#reserved-namespaces">Reser
 </div>
 <h2 id="assumptions-and-considerations"><a class="header" href="#assumptions-and-considerations">Assumptions and Considerations</a></h2>
 <p>Applications MUST refrain from using the <a href="specs/namespace.html#reserved-namespaces">reserved namespaces</a> for their blob data.</p>
-<p>Celestia does not ensure the prevention of non-reserved namespace collisions. 
+<p>Celestia does not ensure the prevention of non-reserved namespace collisions.
 Consequently, two distinct applications might use the same namespace.
 It is the responsibility of these applications to be cautious and manage the implications and consequences arising from such namespace collisions.
 Among the potential consequences is the <em>Woods Attack</em>, as elaborated in this forum post: <a href="https://forum.celestia.org/t/woods-attack-on-celestia/59">Woods Attack on Celestia</a>.</p>

specs/namespace.html

@@ -204,7 +204,7 @@ <h2 id="reserved-namespaces"><a class="header" href="#reserved-namespaces">Reser
 </div>
 <h2 id="assumptions-and-considerations"><a class="header" href="#assumptions-and-considerations">Assumptions and Considerations</a></h2>
 <p>Applications MUST refrain from using the <a href="#reserved-namespaces">reserved namespaces</a> for their blob data.</p>
-<p>Celestia does not ensure the prevention of non-reserved namespace collisions. 
+<p>Celestia does not ensure the prevention of non-reserved namespace collisions.
 Consequently, two distinct applications might use the same namespace.
 It is the responsibility of these applications to be cautious and manage the implications and consequences arising from such namespace collisions.
 Among the potential consequences is the <em>Woods Attack</em>, as elaborated in this forum post: <a href="https://forum.celestia.org/t/woods-attack-on-celestia/59">Woods Attack on Celestia</a>.</p>