Bug 8183 - Spelling fixes
Summary: Spelling fixes
Status: NEW
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Building & Packaging (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: PC Mac OS X
: P2 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-20 19:46 UTC by jsoref
Modified: 2023-08-20 19:46 UTC (History)
0 users



Attachment Type Modified Status Actions Submitter/CLA Status
spelling fixes text/plain None jsoref@gmail.com [NoCLA]

Note You need to log in before you can comment on or make changes to this bug.
Description jsoref 2023-08-20 19:46:08 UTC
Created attachment 5912 [details]
spelling fixes

This is a small series of changes (163 apparently) <https://github.com/jsoref/spamassassin/compare/spell-check...spelling> which I assembled.

Each change/commit should be individually reviewable/discardable. I'm happy to make adjustments.

I've tried to exclude files that didn't seem to be appropriate to change, you can see the patterns I used <https://github.com/jsoref/spamassassin/blob/spell-check/.github/actions/spelling/excludes.txt> / the files I'm checking <https://github.com/jsoref/spamassassin/actions/runs/5919204261/job/16049249308#step:2:693>. E.g., I skipped the `Changes` file because that appeared to be generated from `svn`.

It doesn't look like bugzilla will let me comment on the patch.

So, here are some thoughts:
https://github.com/jsoref/spamassassin/commit/70653597963231eaec63c399aefddc29685557fe `dealy` didn't seem to add much value, so I'm suggesting dropping it.

https://github.com/jsoref/spamassassin/commit/d7b65acde9920e504227b4721e08ec22e5bcf66c -- I'm currently changing `debian/changelog`, but if that's undesired, I can easily drop such changes

https://github.com/jsoref/spamassassin/commit/af5322363008915bf7d4e71ba8a58bbff68f39ce -- there are a couple of places with duplicated words that didn't seem appropriate... There were a couple of cases where they seemed intentional and I've left those alone...

https://github.com/jsoref/spamassassin/commit/54c0fcc02a0653f33797106f54ed899bd5ea28aa -- it's possible this is `dissenting` instead, but ...

https://github.com/jsoref/spamassassin/commit/0bc18be82e5de6c520f235bb4d70e190c385491b -- I'm not sure what the test data here is doing, it didn't seem to care...

https://github.com/jsoref/spamassassin/commit/e957605df1552f94ea819c17c7194b0bd5dc141e -- changes the user facing help output and the docs

https://github.com/jsoref/spamassassin/commit/90a882959f43b088f2315940412d9bc5068ddff4 -- this makes two similar comments more similar by adding a `()`. -- Changes for `into` have been controversial, if people dislike, I'd drop it...

https://github.com/jsoref/spamassassin/commit/f3269ffaf750deaaa7e604faf4a974a0285dd2e7 -- I tried not to mess up alignment, but I missed a spot -- I've fixed the patch without rewriting my branches

https://github.com/jsoref/spamassassin/commit/6d68d3832cf22eb0dd3082569a8f54154b7ebf9c -- I'd be shocked if `MIRRRORED.BY` is the proper spelling...

https://github.com/jsoref/spamassassin/commit/3f28ae572d2a428f777986b85bf140dc41235a3f -- This one puzzled me...

https://github.com/jsoref/spamassassin/commit/86dfd7daee1aa44b35caeff3e153744dff65c71c -- the changes for `non-existent` especially for build/* could easily be wrong

https://github.com/jsoref/spamassassin/commit/b1aa3ead6eb0212f5c5cafc0f0d461e2d795b0b2 -- upon review, I think `occurrence` is the desired text (fixed in patch)

https://github.com/jsoref/spamassassin/commit/925466675a1834e1053c9310b4848dbfcb8fcaeb -- I'm not confident about the change to build/README...

https://github.com/jsoref/spamassassin/commit/7ee6ca8c77180420dc231ed179302670129dc348 -- I've dropped the damaged first hunk...