--- a/ldp-ucr.html	Thu Aug 22 12:38:59 2013 +0100
+++ b/ldp-ucr.html	Thu Aug 22 12:41:06 2013 +0100
@@ -748,7 +748,7 @@
 		These artefacts will be added to the research object throughout the project lifecycle of the project.
 	</p>
 	<p>
-		The RDF description below captures the initial state of the research object. For the purposes of the example, we have included the time of creation. It is a linked data resource addressed via URL from which the following RDF can be retrieved. The null-relative URL <pre>&lt;&gt;</pre> should be understood as a self-reference to the research object itself.
+		The RDF description below captures the initial state of the research object. For the purposes of the example, we have included the time of creation. It is a linked data resource addressed via URL from which the following RDF can be retrieved. The null-relative URL <tt>&lt;&gt;</tt> should be understood as a self-reference to the research object itself.
 	</p>
 	<pre class='example'>
 @prefix ro:  &lt;http://purl.org/wf4ever/ro#&gt; .
@@ -767,9 +767,9 @@
 		The motivation for nested containers comes from the <a>System and Software Development Tool Integration</a> user story. The
 		OSLC Change Management vocabulary allows bug reports to have
 		attachments referenced by the membership predicate
-		<pre>oslc_cm:attachment</pre>. This may be viewed as nested containment. The <pre>top-level-container</pre> contains issues, and
+		<tt>oslc_cm:attachment</tt>. This may be viewed as nested containment. The <tt>top-level-container</tt> contains issues, and
 		each issue is itself a container of attachments.
-		In the example, <pre>issue1234</pre> is a member of the container <pre>top-level-container<pre>. In turn, <pre>attachment324</pre> and <pre>attachment251</pre> are attachments within <pre>issue1234</pre>. Thinking of these as containers makes it easier to manage them as self-contained units.
+		In the example, <tt>issue1234</tt> is a member of the container <tt>top-level-container<tt>. In turn, <tt>attachment324</tt> and <tt>attachment251</tt> are attachments within <tt>issue1234</tt>. Thinking of these as containers makes it easier to manage them as self-contained units.
 	</p>
 	<pre class='example'>
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.