launchpad-reviewers team mailing list archive

Thread
Date

[Merge] lp:~wgrant/launchpad/sharing-help-fixes into lp:launchpad

To: mp+98300@xxxxxxxxxxxxxxxxxx
From: William Grant <me@xxxxxxxxxxxxxxxxxx>
Date: Mon, 19 Mar 2012 23:07:18 -0000
Reply-to: mp+98300@xxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

William Grant has proposed merging lp:~wgrant/launchpad/sharing-help-fixes into lp:launchpad.

Requested reviews:
  Launchpad code reviewers (launchpad-reviewers)

For more details, see:
https://code.launchpad.net/~wgrant/launchpad/sharing-help-fixes/+merge/98300

Fix missing CSS and some typos on /+help-registry/sharing.html
-- 
https://code.launchpad.net/~wgrant/launchpad/sharing-help-fixes/+merge/98300
Your team Launchpad code reviewers is requested to review the proposed merge of lp:~wgrant/launchpad/sharing-help-fixes into lp:launchpad.

=== modified file 'lib/lp/registry/help/sharing.html'
--- lib/lp/registry/help/sharing.html	2012-02-28 21:37:46 +0000
+++ lib/lp/registry/help/sharing.html	2012-03-19 23:06:19 +0000
@@ -3,14 +3,15 @@
 <html>
   <head>
     <title>Sharing kinds of information</title>
-    <link type="text/css" rel="stylesheet"
-        media="screen, print" href="html_files/combo.css" />
-    <link type="text/css" rel="stylesheet"
-        media="screen, print" href="html_files/css.css" />
+    <link rel="stylesheet" type="text/css"
+          href="/+icing/yui/cssreset/reset.css" />
+    <link rel="stylesheet" type="text/css"
+          href="/+icing/yui/cssfonts/fonts.css" />
+    <link rel="stylesheet" type="text/css"
+          href="/+icing/yui/cssbase/base.css" />
   </head>
   <body>
     <h1>Sharing kinds of information</h1>
-    <div class="steps"><div style="width: 100%;" class="step-on"></div></div>
 
     <p>
         Launchpad has three kinds of restricted information &mdash;
@@ -27,9 +28,9 @@
 
     <p>
         If you are a project maintainer, you may need to share a single bug or
-        branch within a project a user or team to address an issue. You can
-        share proprietary, embargoed security, or user-data bugs and branches
-        by subscribing users and teams to the bug or branch. You can then view
+        branch with a user or team to address an issue. You can share
+        proprietary, embargoed security, or user-data bugs and branches by
+        subscribing users and teams to the bug or branch. You can then view
         the exceptional bugs and branches that you've shared.
     </p>
 
@@ -43,7 +44,7 @@
             to people affiliated with the project and its organisation.
         </dd>
 
-        <dt>Embargoes Security</dt>
+        <dt>Embargoed Security</dt>
         <dd>
             Visible if you're involved in fixing and deploying critical
             vulnerability and exploits
@@ -56,10 +57,9 @@
         <dt>User-data</dt>
         <dd>
             Information containing personal data. Visible if you're working
-            with or able to remove, the personal data from the information. It
-            can only be made public after the personal data is removed.
+            with, or able to remove, the personal data from the information.
+            It can only be made public after the personal data is removed.
         </dd>
-
     </dl>
 
     <h2>Sharing</h2>
@@ -73,17 +73,15 @@
 
         <dt>Some</dt>
         <dd>
-            Some Proprietary, embargoed security, or user-data project
+            Some proprietary, embargoed security, or user-data project
             information is shared via a bug or branch subscription.
         </dd>
 
         <dt>Nothing</dt>
         <dd>
-            No Proprietary, embargoed security, or user-data project
+            No proprietary, embargoed security, or user-data project
             information is shared.
         </dd>
     </dl>
-
-
   </body>
 </html>