Making notes consistent with other notes sections in doc

responsible-use/index.html

@@ -356,7 +356,9 @@ <h2>Efficacy of Mobility Data</h2>
             should be undertaken to prove the efficacy of the application before the application is introduced and
             geospatial data captured as a result.
         </p>
-        <div class="note" title="Extensive User testing required to prove underlying technology."></div>
+        <p class="note">
+            Extensive User testing required to prove underlying technology.
+        </p>
         <p>
             There is context to efficacy of course, you might want to try a technique that is unproven if circumstances
             are severe, a global pandemic might be such an example? If so would it be acceptable to experiment first to
@@ -372,7 +374,9 @@ <h2>Efficacy of Mobility Data</h2>
             should only be collected for a particular use – so you would be prevented from using the data later for any
             other purpose.
         </p>
-        <div class="note" title="Data collection for specific purposes limited in coverage."></div>
+        <p class="note">
+            Data collection for specific purposes limited in coverage.">
+        </p>
         <p>
             Related to the temporal aspect of such data collection of course is the spatial context, an application
             collecting information on the movements of a commuter in Paris should not collect data when the user is on
@@ -396,7 +400,9 @@ <h2>Equibility</h2>
             Access to services should not rely on access to expensive sophisticated devices, an alternative needs to be
             available for those without or unwilling to use smartphones for example.
         </p>
-        <div class="note" title="Solutions should be accessible to all members of society."></div>
+        <p class="note">
+            Solutions should be accessible to all members of society.">
+        </p>
         <p>
             Access to technology may also vary for other societal or cultural differences and this may not be easily
             understood or unexpected, it there is an urgent need to build solutions based on ambient location, there
@@ -427,7 +433,9 @@ <h2>Design Choices</h2>
         <p>
             These design principles are by no means comprehensive but a useful starting point.
         </p>
-        <div class="note" title="Location Data collection and or sharing should be voluntary."></div>
+        <p class="note">
+            Location Data collection and or sharing should be voluntary.
+        </p>
         <p>
             It should be clear the collection and sharing of location data are different things. There are many use
             cases that might require a user's location to be obtained, but that data does not need to be stored on
@@ -439,8 +447,10 @@ <h2>Design Choices</h2>
             purposes is not necessary for the operation of the service and you should be able to opt out of this form of
             collection if you wish.
         </p>
-        <div class="note" title="There should be an explicit mechanism to obtain user consent to the collect and then share
-        Ambient Location Information."></div>
+        <p class="note">
+            There should be an explicit mechanism to obtain user consent to the collect and then share Ambient Location
+            Information.
+        </p>
         <p>
             Even if the collection and sharing of location data is not optional there should be an explicit notification
             and ongoing reaffirmation of the users agreement. This is important particularly if location sharing is a
@@ -454,7 +464,9 @@ <h2>Design Choices</h2>
             Again reinforcing the first principle collection and sharing are separate activities and should require
             separate user consent.
         </p>
-        <div class="note" title="The purpose of data collection and/or sharing must be explained."></div>
+        <p class="note">
+            The purpose of data collection and/or sharing must be explained.
+        </p>
         <p>
             This is already a key foundation of most good data protection regulations, you need to explain clearly why
             you are collecting location information and how it will be used.
@@ -465,7 +477,9 @@ <h2>Design Choices</h2>
             you have visited before Apple, if they don’t state they will use the data for that purpose, they must not
             use it ! And to be clear they don’t !
         </p>
-        <div class="note" title="Data Collection/Sharing should be limited in scope."></div>
+        <p class="note">
+            Data Collection/Sharing should be limited in scope.
+        </p>
         <p>
             Again a key data protection principle is to only collect the minimum amount of data required, there is no
             allowable concept of “nice to have in case we need it”.
@@ -483,7 +497,9 @@ <h2>Design Choices</h2>
             injecting random noise into location data so that both the level of privacy and usefulness of the data is
             quantified and controlled.
         </p>
-        <div class="note" title="Data must be kept securely and by default anonymously."></div>
+        <p class="note">
+            Data must be kept securely and by default anonymously.
+        </p>
         <p>
             There needs to be a really, really good reason for Ambient Location information not to be anonymous. For
             most of the current popular applications where Ambient Location information is used to “sense” the world,
@@ -507,7 +523,9 @@ <h2>Design Choices</h2>
             Regardless of where Ambient Location data is stored it should be secure, encrypted both “At Rest” e.g. on
             the device or server but also “In transit” while moving across the network between device and server.
         </p>
-        <div class="note" title="Location data may be Personally Identifiable Information (PII)?"></div>
+        <p class="note">
+            Location data may be Personally Identifiable Information (PII)?
+        </p>
         <p>
             The data that can be considered to be personally identifiable extends beyond the obvious name, address and
             telephone number and there are grey areas specifically with types of Geospatial Information.
@@ -527,7 +545,9 @@ <h2>Design Choices</h2>
             recognised, with metadata of when the image was acquired it is necessary for services such as Google Maps
             “Street View” and Apples “Look Around” to blur faces and car registration plates.
         </p>
-        <div class="note" title="Location data storage must be time & space limited."></div>
+        <p class="note">
+            Location data storage must be time & space limited.
+        </p>
         <p>
             Is the collection of Ambient Location Information temporary and limited to a defined period of storage, and
             if not why not ? Again of course there may be applications where the user might want data to be stored