--- a/bp/index.html	Thu Nov 28 09:29:36 2013 +0100
+++ b/bp/index.html	Thu Nov 28 09:35:21 2013 +0100
@@ -628,17 +628,17 @@
 <p class="informative"> <i>This is intended to be a best-practice guide for data publishers who map existing data to RDF. Assuming they have identified their entity types, and what attributes and relationships are in the data for each entity types, the question is what URIs to choose for the entities. The step-by-step guide should be followed for each entity type individually</i></p>
 
  <p class="highlight"><b>Scope note:</b> <br>
- This is only for choosing identifiers for existing data that is to be translated from a different format or storage technology to RDF. This isn't applicable for authoring fresh data.</p>
-
-<p class="highlight"><b>Assumption:</b> <br>
+ This is only for choosing identifiers for existing data that is to be translated from a different format or storage technology to RDF. This isn't applicable for authoring fresh data.<br>
+ <b>Assumption:</b> <br>
  The input data may change. Therefore, if there are no reliable identifiers/keys in the input, one may not be able to track identity over updates. For the same reason, creating synthetic keys in the conversion process is not possible -- if they're arbitrary, they won't survive inserts/deletes, and if they're based on the input (e.g., hashing some fields) then they won't survive updates to those fields.</p>
 
-<ul class="note">
+<div class="note">
+<ul >
     <li> If Unique Name Assumption doesn't hold for an ID, then don't rely on it too much. Example: Email addresses. A person can have multiple.</li>
     <li>Discuss "authority files", "master data", and how those should be RDFized first. Q: Does your organization or some other reputable body maintain master data or an authority file for the entity type? If so, is it RDFized? If not, can you get that RDFized first? Use their IDs if you can. Otherwise, <b>make your own and do a best-effort mapping.</b></li>
 </ul>
 
-<div class="highlight"><b>Outcome options:</b> <br>
+<b>Outcome options:</b> <br>
    <ol>
     <li> Mint your own URIs. Possibly link to existing URIs.</li>
     <li> Re-use existing URIs.</li>
@@ -672,12 +672,12 @@
 </p>
 
 
-<p class="highlight">Q: Can you map to reliable remote URIs?</b> <br>
+<p class="highlight"><b>Q: Can you map to reliable remote URIs?</b> <br>
 Q: Do you have data about the entities beyond what's already available from the remote URIs?<br>
 A: No? Then use the remote URIs.
 </p>
 
-<p class="highlight">Q: Data is on its own web page with permalink?</b> <br>
+<p class="highlight"><b>Q: Data is on its own web page with permalink?</b> <br>
 Q: Can you deploy RDFa in the web page, or can you deploy Turtle via content negotiation on the same URI?<br>
 A: Use <code>permalink#{fragment}</code> pattern, where <code>{fragment}</code> might be "this", "id", "product", "user", etc.
 </p>