diff --git a/docs/outreach/experience.md b/docs/outreach/experience.md index 5779c83a89..38f8680dc4 100644 --- a/docs/outreach/experience.md +++ b/docs/outreach/experience.md @@ -135,7 +135,7 @@ You can find many examples in the elsewhere, please link to it. Please post each question/problem in a separate message to make it convenient to quote-and-reply to address it. Note that discussions about your work will happen in all the usual places - (#**frontend** , #**backend** , #**design** , etc.), and those are the + (#**frontend**, #**backend**, #**design**, etc.), and those are the streams where you should be _starting_ conversations. Your check-ins are a place to point out where you're feeling stuck, e.g., there was some discussion in a stream or on GitHub, but it seems to have petered out diff --git a/docs/translating/translating.md b/docs/translating/translating.md index c9d8aa4086..029b89cd11 100644 --- a/docs/translating/translating.md +++ b/docs/translating/translating.md @@ -195,7 +195,7 @@ translators can understand and preserve those decisions: Some translated languages don't have these, but we highly encourage translators for new languages (or those updating a language) write a -style guide as they work , since it's easy to take notes as you +style guide as they work, since it's easy to take notes as you translate, and doing so greatly increases the ability of future translators to update the translations in a consistent way. See [our docs on this documentation](../documentation/overview.md) for how to diff --git a/static/js/message_list_view.js b/static/js/message_list_view.js index 87da22e383..dd8b3d12fa 100644 --- a/static/js/message_list_view.js +++ b/static/js/message_list_view.js @@ -1195,7 +1195,7 @@ export class MessageListView { // Ideally, we'd maintain this data structure with a hash // table or at least a pointer from the message containers (in // either case, updating the data structure when message - // groups are merged etc.) , but we only call this from flows + // groups are merged etc.), but we only call this from flows // like message editing, so it's not a big performance // problem. return this._message_groups.find( diff --git a/templates/corporate/for/open-source.html b/templates/corporate/for/open-source.html index 0467200110..ce22a7e0e4 100644 --- a/templates/corporate/for/open-source.html +++ b/templates/corporate/for/open-source.html @@ -367,8 +367,8 @@ discussion work!
diff --git a/templates/zerver/integrations/include/event-filtering-instruction.md b/templates/zerver/integrations/include/event-filtering-instruction.md index e1fd0cbd95..581dbfb651 100644 --- a/templates/zerver/integrations/include/event-filtering-instruction.md +++ b/templates/zerver/integrations/include/event-filtering-instruction.md @@ -6,7 +6,7 @@ Below are the events that {{ integration_display_name }} bot supports: {% set comma = joiner(", ") %} -{% for event_type in all_event_types %} {{- comma() -}} `{{ event_type }}` {% endfor %} +{% for event_type in all_event_types -%} {{- comma() -}} `{{ event_type }}` {%- endfor %} Note that you can also use UNIX-style wildcards like `*` to include multiple events. E.g., `test*` matches every event that starts with diff --git a/zerver/tests/test_openapi.py b/zerver/tests/test_openapi.py index 672f46b208..82921013fa 100644 --- a/zerver/tests/test_openapi.py +++ b/zerver/tests/test_openapi.py @@ -322,7 +322,7 @@ so maybe we shouldn't mark it as intentionally undocumented in the URLs. val = 6 for t in types: if isinstance(t, tuple): - return t # e.g. (list, dict) or (list ,str) + return t # e.g. (list, dict) or (list, str) v = priority.get(t, 6) if v < val: val = v diff --git a/zerver/tests/test_signup.py b/zerver/tests/test_signup.py index 19635a5917..1436eceb37 100644 --- a/zerver/tests/test_signup.py +++ b/zerver/tests/test_signup.py @@ -5499,7 +5499,7 @@ class UserSignUpTest(InviteUserBase): self.assertEqual(result["Location"], "/accounts/login/?email=newuser_email%40zulip.com") self.assertFalse(UserProfile.objects.filter(delivery_email=email).exists()) - # If the user's email is not in the LDAP directory , though, we + # If the user's email is not in the LDAP directory, though, we # successfully create an account with a password in the Zulip # database. password = "nonldappassword" diff --git a/zerver/webhooks/dropbox/doc.md b/zerver/webhooks/dropbox/doc.md index c72c265cf9..3a27c6c416 100644 --- a/zerver/webhooks/dropbox/doc.md +++ b/zerver/webhooks/dropbox/doc.md @@ -10,7 +10,7 @@ Get Dropbox notifications in Zulip! redirected to the **Settings** tab for your app. Scroll down to the **Webhooks** section. -1. Go to the **Oauth 2** section , at the bottom of which you'll find a **Generate** +1. Go to the **Oauth 2** section, at the bottom of which you'll find a **Generate** button. Click on it to activate the app for your account. ![](/static/images/integrations/dropbox/oauth2_generate.png) diff --git a/zilencer/management/commands/populate_db.py b/zilencer/management/commands/populate_db.py index 459e75e02f..bd017553e1 100644 --- a/zilencer/management/commands/populate_db.py +++ b/zilencer/management/commands/populate_db.py @@ -881,7 +881,7 @@ class Command(BaseCommand): "social": {"description": "For socializing"}, "test": {"description": "For testing `code`"}, "errors": {"description": "For errors"}, - # 조리법 - Recipes (Korean) , Пельмени - Dumplings (Russian) + # 조리법 - Recipes (Korean), Пельмени - Dumplings (Russian) "조리법 " + raw_emojis[0]: {"description": "Everything cooking, from pasta to Пельмени"}, }