--- a/ldp-ucr.html	Fri Jul 26 11:15:09 2013 +0100
+++ b/ldp-ucr.html	Fri Jul 26 13:31:55 2013 +0100
@@ -156,7 +156,7 @@
 			informal and can run from one line to a paragraph or two
 			(sometimes described as an 'epic') [[COHN-2004]]. Analysis of each user story will reveal a
 			number of (functional) use cases and other non-functional
-			requirements. See <em>Device API Access Control Use Cases and Requirements</em> [[DAP-REQS]] for a good example
+			requirements. See <i>Device API Access Control Use Cases and Requirements</i> [[DAP-REQS]] for a good example
 			of user stories and their analysis.</li>
 	</ul>
 	<ul>
@@ -169,14 +169,14 @@
 			use case indexing in this document is based on rdb2rdf
 			use cases [[RDB2RDF-UC]]. A variety of styles may be used to capture use cases,
 			from a simple narrative to a structured description with actors,
-			pre/post conditions, step-by-step behaviors (as in POWDER:
-			Use Cases and Requirements [[POWDER-USE-CASES]]), and non-functional requirements
+			pre/post conditions, step-by-step behaviors (as in <i>POWDER:
+			Use Cases and Requirements</i> [[POWDER-USE-CASES]]), and non-functional requirements
 			raised by the use case.</li>
 	</ul>
 	<ul>
 		<li><b>Scenarios</b> are used to model the functional requirements of a use case and focus on a use case in action. Scenarios may range from
-			lightweight narratives as seen in <em>Use
-			cases and requirements for Media Fragments</em> [[MEDIA-FRAGMENTS-REQS]], to being formally
+			lightweight narratives as seen in <i>Use
+			cases and requirements for Media Fragments</i> [[MEDIA-FRAGMENTS-REQS]], to being formally
 			modeled as interaction diagrams. Each use case includes at
 			least a primary scenario, and possibly other alternative
 			scenarios.</li>