--- a/ldp.html	Tue Sep 09 15:19:19 2014 -0400
+++ b/ldp.html	Tue Sep 09 15:55:14 2014 -0400
@@ -898,29 +898,40 @@
 <h2>HTTP GET</h2>
 	<section id="ldprs-get-turtle"><h2 class="normal"><a title="LDP server">LDP servers</a> MUST 
 		respond with a <code>text/turtle</code>
-		representation of the requested <a title="Linked Data Platform RDF Source">LDP-RS</a> [[!turtle]] when
-		the request includes an <code>Accept</code> header, unless content negotiation <em>requires</em> a different outcome.
+		representation of the requested <a title="Linked Data Platform RDF Source">LDP-RS</a> when
+		the request includes an <code>Accept</code> header, unless content negotiation <em>requires</em> a different outcome 
+		[[!turtle]].
+		</h2>
+		<blockquote>
+		<em>Non-normative note: </em>
+		In other words, Turtle must be returned in the usual case clients would expect (client requests it and server
+		supports it) <em>as well as</em> cases where the client requests something, content negotiation results in a tie,
+		and Turtle is one of the tying media types.
 		For example, if the <code>Accept</code> header lists <code>text/turtle</code> as a media type with the
 		highest relative quality
 		factor (<code>q=</code> value), <a title="LDP server">LDP servers</a> must respond with <code>text/turtle</code>
 		even if multiple media types have the same (highest) relative quality factor.
-	</h2></section><!-- Was 4.3.3 / #ldpr-4_3_3 -->
+		On the other hand, if Turtle is one of several requested media types,
+		but another media type the server supports has a higher relative quality factor,
+		normal content negotiation rules apply and the server would not respond with Turtle.
+		</blockquote>
+	</section><!-- Was 4.3.3 / #ldpr-4_3_3 -->
+
+	<section id="ldprs-get-conneg"><h2 class="normal"><a title="LDP server">LDP servers</a> SHOULD
+		respond with a <code>text/turtle</code>
+		representation of the requested <a title="Linked Data Platform RDF Source">LDP-RS</a> whenever 
+		the <code>Accept</code> request header is absent [[!turtle]].  
+	</h2></section><!-- new -->
 
 	<div class="atrisk" id="atrisk-ldpr-jsonld"><p class="atrisktext">Feature At Risk</p>
 	<p>The LDP Working Group proposes incorporation of the following clause requiring JSON-LD support.</p>
 	</div>
 	<section id="ldprs-get-jsonld"><h2 class="normal"><a title="LDP server">LDP servers</a> MUST 
 		respond with a <code>application/ld+json</code>
-		representation of the requested <a title="Linked Data Platform RDF Source">LDP-RS</a> [[!JSON-LD]]
+		representation of the requested <a title="Linked Data Platform RDF Source">LDP-RS</a>
 		when the request includes an <code>Accept</code> header, unless content negotiation 
 		or <a href="#ldprs-get-turtle">Turtle support</a>
-		<em>requires</em> a different outcome.
-	</h2></section><!-- new -->
-
-	<section id="ldprs-get-conneg"><h2 class="normal"><a title="LDP server">LDP servers</a> SHOULD
-		respond with a <code>text/turtle</code>
-		representation of the requested <a title="Linked Data Platform RDF Source">LDP-RS</a> whenever 
-		the <code>Accept</code> request header is absent.  
+		<em>requires</em> a different outcome [[!JSON-LD]].
 	</h2></section><!-- new -->
 
 </section> <!-- ldprs-HTTP_GET -->