Launchpad itself

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

  1. sharing-help-fixes
  2. Merge into devel
Proposed by William Grant on 2012-03-19
Status: Merged
Approved by: Curtis Hovey on 2012-03-19
Approved revision: no longer in the source branch.
Merged at revision: 14974
Proposed branch: lp:~wgrant/launchpad/sharing-help-fixes
Merge into: lp:launchpad
Diff against target: 79 lines (+14/-16)
1 file modified
lib/lp/registry/help/sharing.html (+14/-16)
To merge this branch: bzr merge lp:~wgrant/launchpad/sharing-help-fixes
Reviewer Review Type Date Requested Status
Curtis Hovey (community) code 2012-03-19 Approve on 2012-03-19
Review via email: mp+98300@code.launchpad.net

Commit Message

Fix missing CSS and some typos on /+help-registry/sharing.html

Description of the Change

Fix missing CSS and some typos on /+help-registry/sharing.html

To post a comment you must log in.
Curtis Hovey (sinzui) wrote :

Thank you.

review: Approve (code)

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'lib/lp/registry/help/sharing.html'
2--- lib/lp/registry/help/sharing.html 2012-02-28 21:37:46 +0000
3+++ lib/lp/registry/help/sharing.html 2012-03-19 23:09:32 +0000
4@@ -3,14 +3,15 @@
5 <html>
6 <head>
7 <title>Sharing kinds of information</title>
8- <link type="text/css" rel="stylesheet"
9- media="screen, print" href="html_files/combo.css" />
10- <link type="text/css" rel="stylesheet"
11- media="screen, print" href="html_files/css.css" />
12+ <link rel="stylesheet" type="text/css"
13+ href="/+icing/yui/cssreset/reset.css" />
14+ <link rel="stylesheet" type="text/css"
15+ href="/+icing/yui/cssfonts/fonts.css" />
16+ <link rel="stylesheet" type="text/css"
17+ href="/+icing/yui/cssbase/base.css" />
18 </head>
19 <body>
20 <h1>Sharing kinds of information</h1>
21- <div class="steps"><div style="width: 100%;" class="step-on"></div></div>
22
23 <p>
24 Launchpad has three kinds of restricted information &mdash;
25@@ -27,9 +28,9 @@
26
27 <p>
28 If you are a project maintainer, you may need to share a single bug or
29- branch within a project a user or team to address an issue. You can
30- share proprietary, embargoed security, or user-data bugs and branches
31- by subscribing users and teams to the bug or branch. You can then view
32+ branch with a user or team to address an issue. You can share
33+ proprietary, embargoed security, or user-data bugs and branches by
34+ subscribing users and teams to the bug or branch. You can then view
35 the exceptional bugs and branches that you've shared.
36 </p>
37
38@@ -43,7 +44,7 @@
39 to people affiliated with the project and its organisation.
40 </dd>
41
42- <dt>Embargoes Security</dt>
43+ <dt>Embargoed Security</dt>
44 <dd>
45 Visible if you're involved in fixing and deploying critical
46 vulnerability and exploits
47@@ -56,10 +57,9 @@
48 <dt>User-data</dt>
49 <dd>
50 Information containing personal data. Visible if you're working
51- with or able to remove, the personal data from the information. It
52- can only be made public after the personal data is removed.
53+ with, or able to remove, the personal data from the information.
54+ It can only be made public after the personal data is removed.
55 </dd>
56-
57 </dl>
58
59 <h2>Sharing</h2>
60@@ -73,17 +73,15 @@
61
62 <dt>Some</dt>
63 <dd>
64- Some Proprietary, embargoed security, or user-data project
65+ Some proprietary, embargoed security, or user-data project
66 information is shared via a bug or branch subscription.
67 </dd>
68
69 <dt>Nothing</dt>
70 <dd>
71- No Proprietary, embargoed security, or user-data project
72+ No proprietary, embargoed security, or user-data project
73 information is shared.
74 </dd>
75 </dl>
76-
77-
78 </body>
79 </html>