This could probably be tackled in a separate PR, but I'd recommend imperative language for describing added features:

"Copy canonical link to file" vs "Copies canonical link to file" across all features. This follows popular commit convention by Linus Torvalds. The reasoninng is that you instruct Git to apply that change if you pick this commit. In the same way, you instruct the extension if you have that feature. It's similar to changelog formats based on commit messages following that convention. I guess I'm probably used to that, but I still like the brevity and clarity of the imperative form.

@hkdobrev sounds good.

I'd add dropping lets you/allows. Examples:

- Allows you to toggle all outdated PR comments or PR/Commit files with <kbd>alt</kbd> <kbd>click</kbd>
+ Toggle all outdated PR comments or PR/Commit files with <kbd>alt</kbd> <kbd>click</kbd>

- Makes it possible to automatically merge a PR after its build has passed
+ Automatically merge a PR after its build has passed (checkbox)

- Supports indenting with the tab key in textareas like the comment box (<kbd>shift</kbd> <kbd>tab</kbd> for original behavior)
+ Indent with the <kbd>tab</kbd> key in textareas like the comment box (<kbd>shift</kbd> <kbd>tab</kbd> for original behavior)

@hkdobrev @bfred-it There's a difference between Refined GitHub doing something by default (decluttering the UI) and it allowing the user to do something (copying a link).

Using the same style for both cases might make users think Refined GitHub does things by default that actually have to be explicitly triggered/enabled by them.

For reference, that’s also how Apple talks about what their software lets you do:

Open a picture in a third‑party photo editing app like Photoshop or Pixelmator directly from Photos, and your edits will automatically be saved in your Photos library. You can also download third‑party project extensions from the Mac App Store that let you order framed prints, create web pages, and more, right from the Photos app.

Personalize your browsing experience in Safari by enabling settings for individual websites, like page zoom level, location services, notifications, and content blockers. So each website appears just how you like it.

Easily make sophisticated contrast and color adjustments to your photos with powerful tools like Curves for fine‑tuning contrast and Selective Color to make any color more saturated. And new, professionally inspired filters let you quickly give your pictures a distinctive look.

Instantly filter photo collections by your favorite criteria. A new selection counter keeps track of what you’ve selected, and lets you drag and drop collected images into an album or export them to the desktop. You can also rotate and favorite batches of images right from the toolbar.

For reference, that’s also how Apple talks about what their software lets you do:

I like the style they use. Adopting it requires adding the features' uses to the current descriptions that just say what they do. Here are a few examples:

• Adds a Trending link to the global navbar. (g t hotkey)
  • Access the trending repositories with a link in the global navbar or the g t hotkey.
• Adds ↑ shortcut for editing your last comment
  • Quickly edit your last comment using the ↑ shortcut.
• Moves destructive buttons in commenting forms away from the primary button
  • No longer click destructive buttons on accident as they're moved away from the primary button.

What do you think about rewording the features in this way?

Love it! The third one is a bit awkward, maybe it could be made passive:

• Destructive buttons are moved away from the primary button

Random ping: @shroudedcode resolve this before we have any merge conflicts later!

@ramlmn I'll fix the merge conflict on the weekend. I'm doing an internship this week and can barely focus on doing any kind of open source work in the evening. Also, please stop pinging people about their pull requests unless the pull request is really old and they have been active within the last few days (a sign that they might have actually forgotten about it). It comes off rude and often they have reasons for "abandoning" them for a while.

The pull request is by the way ready for review again. @bfred-it @hkdobrev

Sorry! Lots of notes. I should have just made the changes where I was sure

Regarding the things I haven't changed yet:

I'm trying to use the same style for all features: A sentence starting with an imaginary Refined GitHub allows you to … Having features that use a different style in between the others looks weird and is harder to read. I agree that some of the features still sound kind of awkward. If you have any suggestions on how to improve them while adhering to the style, let me know.

I don’t think we can stick to just that. It’s preferrable to keep sentences short and readable instead, given that there’s a lot of them.

• People have fled

Is preferrable to

• The boats have allowed people to flee

I've changed some of the features to sound less awkward and made sure that within a section they all use the same style. While for most features the "Apple style" works best (in my opinion), using the style for Declutter and UI improvements sounds awkward. That's why I've reworded them to use a different style.

I still can't get myself to use multiple different styles within a section. It just looks so wrong.

Alright let's merge this soon, at least partially, @shroudedcode doesn't have to deal with insane merge conflicts. Further changes can be suggested later.

I'm going through it and making small changes

@shroudedcode thanks for this PR!

I just had to make many of them passive because this was just too awkward:

Quickly determine what file you're looking at with the sticky file headers on pull requests.

and can just be:

File headers are always visible when scrolling.

Apple-like copy works when you can take an action, but not when things are.

"Quickly see this and that" everywhere is just extra copy.