Merge ~lgp171188/launchpad:codespell-bugs into launchpad:master

[Guruprasad]

Fix spelling errors in lp.bugs

[Colin Watson (cjwatson)]

review: Approve

diff --git a/lib/lp/bugs/browser/bugtarget.py b/lib/lp/bugs/browser/bugtarget.py
index ed93035..0d7f4af 100644
--- a/lib/lp/bugs/browser/bugtarget.py
+++ b/lib/lp/bugs/browser/bugtarget.py
@@ -858,7 +858,7 @@ class FileBugViewBase(LaunchpadFormView):
     default_bug_reported_acknowledgement = "Thank you for your bug report."
 
     def getAcknowledgementMessage(self, context):
-        """An acknowlegement message displayed to the user."""
+        """An acknowledgement message displayed to the user."""
         # If a given context does not have a custom message, we go up in the
         # "object hierarchy" until we find one. If no customized messages
         # exist for any context, a default message is returned.
diff --git a/lib/lp/bugs/doc/externalbugtracker-debbugs.rst b/lib/lp/bugs/doc/externalbugtracker-debbugs.rst
index b26f84f..80bd099 100644
--- a/lib/lp/bugs/doc/externalbugtracker-debbugs.rst
+++ b/lib/lp/bugs/doc/externalbugtracker-debbugs.rst
@@ -206,7 +206,7 @@ there's no way of knowing if the bug is confirmed or not.
     New
 
 If the 'wontfix' tag is present we map it to "Won't Fix". The 'wontfix'
-tag takes precedence over the confimed tags (help, confirmed, upstream,
+tag takes precedence over the confirmed tags (help, confirmed, upstream,
 fixed-upstream) since 'wontfix' is the state after confirmed. The 'wontfix'
 tag also takes precedence over the fix-committed tags (pending, fixed,
 fixed-in-experimental) since the malone status will correctly change to
diff --git a/lib/lp/bugs/externalbugtracker/mantis.py b/lib/lp/bugs/externalbugtracker/mantis.py
index 9c6083b..9554143 100644
--- a/lib/lp/bugs/externalbugtracker/mantis.py
+++ b/lib/lp/bugs/externalbugtracker/mantis.py
@@ -448,7 +448,7 @@ class Mantis(ExternalBugTracker):
         ("assigned", BugTaskStatus.INPROGRESS),
         ("feedback", BugTaskStatus.INCOMPLETE),
         ("new", BugTaskStatus.NEW),
-        ("confirmed", "ackowledged", BugTaskStatus.CONFIRMED),
+        ("confirmed", "acknowledged", BugTaskStatus.CONFIRMED),
         (
             "resolved",
             "closed",
diff --git a/lib/lp/bugs/mail/tests/test_handler.py b/lib/lp/bugs/mail/tests/test_handler.py
index fd60ba1..c193437 100644
--- a/lib/lp/bugs/mail/tests/test_handler.py
+++ b/lib/lp/bugs/mail/tests/test_handler.py
@@ -307,14 +307,14 @@ class MaloneHandlerProcessTestCase(TestCaseWithFactory):
         handler = MaloneHandler()
         with person_logged_in(project.owner):
             msg = self.factory.makeSignedMessage(
-                body="unsecure\n security yes\n affects fnord\n tag ajax",
-                subject="unsecure code",
+                body="insecure\n security yes\n affects fnord\n tag ajax",
+                subject="insecure code",
                 to_address="[e-mail]",
             )
             handler.process(msg, msg["To"])
         notification = self.getLatestBugNotification()
         bug = notification.bug
-        self.assertEqual("unsecure code", bug.title)
+        self.assertEqual("insecure code", bug.title)
         self.assertTrue(bug.security_related)
         self.assertEqual(["ajax"], bug.tags)
         self.assertEqual(1, len(bug.bugtasks))
@@ -354,14 +354,14 @@ class MaloneHandlerProcessTestCase(TestCaseWithFactory):
         handler = MaloneHandler()
         with person_logged_in(project.owner):
             msg = self.factory.makeSignedMessage(
-                body="unsecure\n informationtype userdata\n affects fnord",
-                subject="unsecure code",
+                body="insecure\n informationtype userdata\n affects fnord",
+                subject="insecure code",
                 to_address="[e-mail]",
             )
             handler.process(msg, msg["To"])
         notification = self.getLatestBugNotification()
         bug = notification.bug
-        self.assertEqual("unsecure code", bug.title)
+        self.assertEqual("insecure code", bug.title)
         self.assertEqual(InformationType.USERDATA, bug.information_type)
         self.assertEqual(1, len(bug.bugtasks))
         self.assertEqual(project, bug.bugtasks[0].target)
diff --git a/lib/lp/bugs/model/structuralsubscription.py b/lib/lp/bugs/model/structuralsubscription.py
index dff0e8f..a5c9519 100644
--- a/lib/lp/bugs/model/structuralsubscription.py
+++ b/lib/lp/bugs/model/structuralsubscription.py
@@ -750,7 +750,7 @@ def _get_structural_subscription_filter_id_query(
     # we can get the full set of what we need in subsuming or
     # subsequent SQL calls.
     # (Aside 1: We could in theory get all the fields we wanted with
-    # a hack--we could use an aggregrate function like max to get
+    # a hack--we could use an aggregate function like max to get
     # fields that we know will be unique--but Storm would not like
     # it.)
     # (Aside 2: IMO Postgres should allow getting other fields if
diff --git a/lib/lp/bugs/model/vulnerability.py b/lib/lp/bugs/model/vulnerability.py
index 846ea55..53eef9d 100644
--- a/lib/lp/bugs/model/vulnerability.py
+++ b/lib/lp/bugs/model/vulnerability.py
@@ -434,7 +434,7 @@ def get_vulnerability_privacy_filter(user):
     access to, including private vulnerabilities where the user has proper
     permission.
 
-    :param user: An IPerson, or a class attribute tha references an IPerson
+    :param user: An IPerson, or a class attribute that references an IPerson
                  in the database.
     :return: A Storm condition.
     """
diff --git a/lib/lp/bugs/stories/bugs/xx-bug-comments-truncated.rst b/lib/lp/bugs/stories/bugs/xx-bug-comments-truncated.rst
index c664ab9..5b02254 100644
--- a/lib/lp/bugs/stories/bugs/xx-bug-comments-truncated.rst
+++ b/lib/lp/bugs/stories/bugs/xx-bug-comments-truncated.rst
@@ -85,7 +85,7 @@ The whole comment is visible on this page:
          itemprop="commentText"><p>This would be a real killer feature.
       If there is already code
       to make it possible, why aren't there tons of press announcements
-      about the secuirty possibilities. Imagine - no more embarrassing
+      about the security possibilities. Imagine - no more embarrassing
       emails for ... disappear! I'm sure Redmond will switch over as soon as
       they hear about this. It's not a bug, it's a feature!</p></div>
     </div>
diff --git a/lib/lp/bugs/stories/guided-filebug/xx-bug-reporting-guidelines.rst b/lib/lp/bugs/stories/guided-filebug/xx-bug-reporting-guidelines.rst
index 67eb70a..ccf9feb 100644
--- a/lib/lp/bugs/stories/guided-filebug/xx-bug-reporting-guidelines.rst
+++ b/lib/lp/bugs/stories/guided-filebug/xx-bug-reporting-guidelines.rst
@@ -2,7 +2,7 @@ Bug Reporting Guidelines and acknowledgement messages
 =====================================================
 
 Some helpful explanatory text - guidelines - can be set for
-distributions, product groups, products, and source packages, as wel
+distributions, product groups, products, and source packages, as well
 as an acknowledgement message that is displayed when a bug has been
 filed.
 
diff --git a/lib/lp/bugs/tests/externalbugtracker.py b/lib/lp/bugs/tests/externalbugtracker.py
index 6a126b5..e0e84db 100644
--- a/lib/lp/bugs/tests/externalbugtracker.py
+++ b/lib/lp/bugs/tests/externalbugtracker.py
@@ -1521,7 +1521,7 @@ class TestTracXMLRPCTransport(RequestsTransport):
                 for bug in bugs_to_return
             ]
         # At level 3, we return the full comment dicts along with the
-        # bug metadata. Tne comment dicts do not include the user field,
+        # bug metadata. The comment dicts do not include the user field,
         # however.
         elif level == LP_PLUGIN_FULL:
             bugs_to_return = [
diff --git a/lib/lp/bugs/tests/test_bugnotification.py b/lib/lp/bugs/tests/test_bugnotification.py
index 063c64c..47f764e 100644
--- a/lib/lp/bugs/tests/test_bugnotification.py
+++ b/lib/lp/bugs/tests/test_bugnotification.py
@@ -397,7 +397,7 @@ class TestNotificationsLinkToFilters(TestCaseWithFactory):
 
 
 class TestNotificationProcessingWithoutRecipients(TestCaseWithFactory):
-    """Adding notificatons without any recipients does not cause any harm.
+    """Adding notifications without any recipients does not cause any harm.
 
     In some cases, we may have attempts to send bug notifications for bugs
     that do not have any notification recipients.