docs/integrations/builtin/credentials/azureopenai.md|27 col 22| [from-write-good.Passive] 'is created' may be passive voice. Use active voice if you can.
docs/integrations/builtin/credentials/azureopenai.md|31 col 20| [from-write-good.Passive] 'is deployed' may be passive voice. Use active voice if you can.

docs/user-management/saml/managing.md|9 col 43| [from-write-good.Passive] 'are affected' may be passive voice. Use active voice if you can.
docs/user-management/saml/troubleshooting.md|13 col 76| [from-write-good.Passive] 'is formatted' may be passive voice. Use active voice if you can.
docs/user-management/saml/troubleshooting.md|13 col 89| [from-write-good.Weasel] 'correctly' is a weasel word!
docs/external-secrets.md|22 col 59| [from-alex.Ablist] When referring to a person, consider using 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'special'.
docs/user-management/saml/okta.md|54 col 65| [from-write-good.Weasel] 'currently' is a weasel word!
docs/user-management/account-types.md|25 col 4| [from-write-good.TooWordy] 'Modify' is too wordy.
docs/user-management/account-types.md|33 col 1| [from-microsoft.We] Try to avoid using first-person plural like 'We'.
docs/user-management/ldap.md|31 col 157| [from-write-good.Passive] 'are excluded' may be passive voice. Use active voice if you can.
docs/contributing.md|6 col 24| [from-microsoft.HeadingPunctuation] Don't use end punctuation in headings.
docs/contributing.md|8 col 143| [from-microsoft.We] Try to avoid using first-person plural like 'us'.
docs/contributing.md|10 col 28| [from-microsoft.We] Try to avoid using first-person plural like 'us'.
docs/contributing.md|13 col 10| [from-microsoft.We] Try to avoid using first-person plural like 'us'.
docs/contributing.md|20 col 9| [from-write-good.TooWordy] 'participate' is too wordy.
docs/contributing.md|45 col 7| [from-write-good.TooWordy] 'additional' is too wordy.
docs/contributing.md|62 col 128| [from-write-good.TooWordy] 'However' is too wordy.
docs/contributing.md|62 col 179| [from-microsoft.We] Try to avoid using first-person plural like 'our'.
docs/contributing.md|69 col 125| [from-write-good.Passive] 'being used' may be passive voice. Use active voice if you can.
docs/contributing.md|96 col 76| [from-write-good.TooWordy] 'implement' is too wordy.
docs/contributing.md|100 col 23| [from-microsoft.Wordiness] Consider using 'about' instead of 'an estimated'.
docs/contributing.md|102 col 18| [from-write-good.Passive] 'is published' may be passive voice. Use active voice if you can.
docs/contributing.md|106 col 57| [from-microsoft.We] Try to avoid using first-person plural like 'our'.
docs/contributing.md|106 col 154| [from-microsoft.We] Try to avoid using first-person plural like 'us'.
docs/contributing.md|106 col 169| [from-microsoft.We] Try to avoid using first-person plural like 'we'.
docs/contributing.md|106 col 208| [from-write-good.Weasel] 'successfully' is a weasel word!
docs/contributing.md|111 col 302| [from-microsoft.We] Try to avoid using first-person plural like 'our'.
docs/contributing.md|112 col 20| [from-microsoft.We] Try to avoid using first-person plural like 'We'.
docs/contributing.md|113 col 45| [from-write-good.Weasel] 'successfully' is a weasel word!
docs/contributing.md|113 col 92| [from-microsoft.We] Try to avoid using first-person plural like 'we'.
docs/user-management/saml/setup.md|53 col 95| [from-microsoft.We] Try to avoid using first-person plural like 'us'.
docs/user-management/saml/setup.md|56 col 67| [from-microsoft.We] Try to avoid using first-person plural like 'us'.
docs/flow-logic/error-handling.md|8 col 118| [from-write-good.Weasel] 'gracefully' is a weasel word!
docs/flow-logic/error-handling.md|8 col 118| [from-microsoft.Adverbs] Consider removing 'gracefully'.
docs/flow-logic/error-handling.md|31 col 81| [from-write-good.Weasel] 'Usually' is a weasel word!
docs/embed/workflow-templates.md|43 col 23| [from-microsoft.We] Try to avoid using first-person plural like 'us'.
docs/embed/deployment.md|19 col 25| [from-write-good.Weasel] 'nightly' is a weasel word!
docs/embed/index.md|13 col 64| [from-write-good.Weasel] 'many' is a weasel word!
docs/flow-logic/looping.md|7 col 80| [from-write-good.Weasel] 'repeatedly' is a weasel word!
docs/flow-logic/looping.md|7 col 80| [from-microsoft.Adverbs] Consider removing 'repeatedly'.
docs/flow-logic/looping.md|15 col 7| [from-write-good.Weasel] 'usually' is a weasel word!
docs/flow-logic/looping.md|32 col 61| [from-write-good.TooWordy] 'However' is too wordy.
docs/flow-logic/looping.md|34 col 28| [from-write-good.Passive] 'is met' may be passive voice. Use active voice if you can.
docs/flow-logic/looping.md|42 col 26| [from-write-good.Passive] 'are processed' may be passive voice. Use active voice if you can.
docs/flow-logic/looping.md|44 col 135| [from-write-good.Passive] 'are processed' may be passive voice. Use active voice if you can.
docs/flow-logic/looping.md|66 col 106| [from-write-good.TooWordy] 'additional' is too wordy.
docs/flow-logic/looping.md|73 col 226| [from-write-good.TooWordy] 'However' is too wordy.
docs/flow-logic/looping.md|73 col 247| [from-write-good.Passive] 'is referenced' may be passive voice. Use active voice if you can.
docs/embed/prerequisites.md|19 col 121| [from-write-good.Weasel] 'Usually' is a weasel word!
docs/embed/prerequisites.md|34 col 63| [from-write-good.Passive] 'is persisted' may be passive voice. Use active voice if you can.
docs/embed/prerequisites.md|34 col 141| [from-write-good.Passive] 'is lost' may be passive voice. Use active voice if you can.
docs/embed/prerequisites.md|35 col 80| [from-write-good.Passive] 'be deprecated' may be passive voice. Use active voice if you can.
docs/embed/prerequisites.md|35 col 94| [from-write-good.TooWordy] 'in the near future' is too wordy.
docs/embed/prerequisites.md|41 col 184| [from-write-good.Passive] 'being processed' may be passive voice. Use active voice if you can.
docs/embed/white-labelling.md|39 col 92| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/embed/white-labelling.md|41 col 84| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/embed/white-labelling.md|42 col 89| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/embed/white-labelling.md|67 col 109| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/embed/white-labelling.md|78 col 56| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/embed/white-labelling.md|85 col 159| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/embed/white-labelling.md|114 col 226| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/embed/white-labelling.md|118 col 137| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/embed/white-labelling.md|135 col 70| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/embed/white-labelling.md|136 col 96| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/embed/managing-workflows.md|9 col 92| [from-write-good.Weasel] 'likely' is a weasel word!
docs/embed/managing-workflows.md|26 col 3| [from-write-good.TooWordy] 'Obtain' is too wordy.
docs/embed/managing-workflows.md|26 col 49| [from-write-good.TooWordy] 'additional' is too wordy.
docs/embed/managing-workflows.md|26 col 80| [from-write-good.Passive] 'be required' may be passive voice. Use active voice if you can.
docs/embed/managing-workflows.md|30 col 8| [from-write-good.TooWordy] 'Obtain' is too wordy.
docs/embed/managing-workflows.md|32 col 112| [from-write-good.TooWordy] 'additional' is too wordy.
docs/embed/managing-workflows.md|36 col 44| [from-write-good.Passive] 'been obtained' may be passive voice. Use active voice if you can.
docs/embed/managing-workflows.md|36 col 135| [from-write-good.Passive] 'be done' may be passive voice. Use active voice if you can.
docs/embed/managing-workflows.md|50 col 49| [from-write-good.Passive] 'be called' may be passive voice. Use active voice if you can.
docs/embed/managing-workflows.md|103 col 83| [from-write-good.Passive] 'be duplicated' may be passive voice. Use active voice if you can.
docs/embed/managing-workflows.md|365 col 13| [from-write-good.TooWordy] 'additional' is too wordy.
docs/embed/managing-workflows.md|376 col 35| [from-write-good.TooWordy] 'implement' is too wordy.
docs/embed/managing-workflows.md|378 col 3| [from-write-good.TooWordy] 'Obtain' is too wordy.
docs/embed/managing-workflows.md|378 col 49| [from-write-good.TooWordy] 'additional' is too wordy.
docs/embed/managing-workflows.md|378 col 80| [from-write-good.Passive] 'be required' may be passive voice. Use active voice if you can.
docs/embed/managing-workflows.md|378 col 120| [from-write-good.TooWordy] 'Obtain' is too wordy.
docs/embed/managing-workflows.md|385 col 50| [from-microsoft.Adverbs] Consider removing 'greatly'.
docs/embed/managing-workflows.md|385 col 96| [from-write-good.TooWordy] 'however' is too wordy.
docs/embed/managing-workflows.md|385 col 116| [from-write-good.Weasel] 'few' is a weasel word!
docs/embed/managing-workflows.md|387 col 22| [from-write-good.Passive] 'be triggered' may be passive voice. Use active voice if you can.
docs/embed/managing-workflows.md|389 col 42| [from-write-good.Passive] 'are needed' may be passive voice. Use active voice if you can.
docs/embed/managing-workflows.md|390 col 63| [from-write-good.Passive] 'is selected' may be passive voice. Use active voice if you can.
docs/embed/managing-workflows.md|394 col 52| [from-write-good.Passive] 'be needed' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|25 col 27| [from-write-good.Passive] 'be set' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|33 col 155| [from-write-good.Passive] 'be made' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|36 col 19| [from-write-good.Passive] 'be called' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|69 col 34| [from-write-good.Passive] 'are based' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|70 col 95| [from-write-good.Passive] 'be used' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|75 col 11| [from-write-good.Weasel] 'many' is a weasel word!
docs/embed/configuration.md|97 col 110| [from-write-good.Passive] 'be used' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|99 col 98| [from-write-good.Passive] 'are saved' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|101 col 62| [from-write-good.Passive] 'be used' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|103 col 156| [from-write-good.Passive] 'be used' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|104 col 224| [from-write-good.Passive] 'be used' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|105 col 102| [from-write-good.Passive] 'be used' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|108 col 100| [from-write-good.Passive] 'be used' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|116 col 7| [from-write-good.Passive] 'are set' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|117 col 19| [from-write-good.Passive] 'is done' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|119 col 18| [from-write-good.Passive] 'be set' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|161 col 1| [from-write-good.Weasel] 'Additionally' is a weasel word!
docs/embed/configuration.md|161 col 37| [from-write-good.Passive] 'be accessed' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|165 col 145| [from-write-good.Passive] 'is performed' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|165 col 168| [from-write-good.Passive] 'be used' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|171 col 87| [from-write-good.Passive] 'is changed' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|172 col 55| [from-write-good.Passive] 'is created' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|175 col 83| [from-write-good.Passive] 'is selected' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|176 col 56| [from-write-good.Passive] 'is opened' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|177 col 62| [from-write-good.Passive] 'is selected' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|181 col 68| [from-write-good.Passive] 'been made' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|196 col 61| [from-write-good.Passive] 'is updated' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|199 col 54| [from-write-good.Passive] 'is executed' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|201 col 76| [from-write-good.Passive] 'are saved' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|205 col 11| [from-write-good.Passive] 'be set' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|242 col 29| [from-write-good.Passive] 'be defined' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|242 col 69| [from-write-good.Passive] 'is invoked' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|244 col 39| [from-write-good.Passive] 'be used' may be passive voice. Use active voice if you can.
docs/embed/configuration.md|245 col 74| [from-write-good.Weasel] 'exactly' is a weasel word!
docs/workflows/create.md|15 col 107| [from-write-good.Weasel] 'quickly' is a weasel word!
docs/workflows/create.md|15 col 107| [from-microsoft.Adverbs] Consider removing 'quickly'.
docs/workflows/create.md|31 col 68| [from-write-good.Passive] 'are met' may be passive voice. Use active voice if you can.
docs/workflows/sharing.md|26 col 11| [from-write-good.Passive] 'are logged' may be passive voice. Use active voice if you can.
docs/workflows/sharing.md|33 col 38| [from-microsoft.Wordiness] Consider using 'unless' instead of 'except when'.
docs/workflows/index.md|17 col 107| [from-write-good.Weasel] 'quickly' is a weasel word!
docs/workflows/index.md|17 col 107| [from-microsoft.Adverbs] Consider removing 'quickly'.
docs/workflows/components/sticky-notes.md|10 col 35| [from-microsoft.Adverbs] Consider removing 'heavily'.
docs/workflows/components/sticky-notes.md|10 col 44| [from-write-good.Weasel] 'especially' is a weasel word!
docs/workflows/components/nodes.md|29 col 198| [from-write-good.TooWordy] 'However' is too wordy.
docs/workflows/components/nodes.md|66 col 111| [from-write-good.TooWordy] 'additional' is too wordy.
docs/api/index.md|8 col 58| [from-write-good.Weasel] 'many' is a weasel word!
docs/api/index.md|24 col 73| [from-microsoft.We] Try to avoid using first-person plural like 'US'.
docs/api/index.md|24 col 193| [from-write-good.TooWordy] 'indicate' is too wordy.
docs/api/index.md|24 col 206| [from-write-good.TooWordy] 'type of' is too wordy.
docs/api/index.md|27 col 221| [from-write-good.Weasel] 'safely' is a weasel word!
docs/api/index.md|27 col 221| [from-microsoft.Adverbs] Consider removing 'safely'.
docs/source-control-environments/using/manage-variables.md|43 col 45| [from-write-good.Weasel] 'safely' is a weasel word!
docs/source-control-environments/using/manage-variables.md|43 col 45| [from-microsoft.Adverbs] Consider removing 'safely'.
docs/source-control-environments/using/push-pull.md|32 col 135| [from-write-good.Weasel] 'few' is a weasel word!
docs/source-control-environments/using/push-pull.md|56 col 40| [from-write-good.Passive] 'is opinionated' may be passive voice. Use active voice if you can.
docs/source-control-environments/using/push-pull.md|66 col 50| [from-write-good.Weasel] 'immediately' is a weasel word!
docs/source-control-environments/understand/environments.md|39 col 472| [from-microsoft.Adverbs] Consider removing 'partially'.
docs/source-control-environments/understand/patterns.md|37 col 105| [from-write-good.Weasel] 'likely' is a weasel word!
docs/source-control-environments/understand/git.md|9 col 129| [from-write-good.TooWordy] 'implement' is too wordy.
docs/source-control-environments/understand/git.md|16 col 63| [from-write-good.Weasel] 'exactly' is a weasel word!
docs/source-control-environments/understand/git.md|30 col 293| [from-write-good.Passive] 'is merged' may be passive voice. Use active voice if you can.
docs/source-control-environments/create-environments.md|87 col 40| [from-write-good.Weasel] 'few' is a weasel word!
docs/langchain/langchain-tutorial.md|8 col 132| [from-write-good.TooWordy] 'However' is too wordy.
docs/langchain/langchain-tutorial.md|207 col 125| [from-microsoft.FirstPerson] Use first person (such as 'me') sparingly.
docs/langchain/langchain-n8n.md|31 col 101| [from-write-good.Passive] 'be provided' may be passive voice. Use active voice if you can.
docs/data/data-pinning.md|10 col 83| [from-write-good.Weasel] 'repeatedly' is a weasel word!
docs/data/data-pinning.md|10 col 83| [from-microsoft.Adverbs] Consider removing 'repeatedly'.
docs/data/data-mapping/data-item-linking/index.md|13 col 26| [from-write-good.TooWordy] 'implement' is too wordy.
docs/data/data-mapping/data-item-linking/item-linking-concepts.md|7 col 230| [from-write-good.Passive] 'be complicated' may be passive voice. Use active voice if you can.
docs/data/data-mapping/data-item-linking/item-linking-concepts.md|7 col 260| [from-write-good.Weasel] 'especially' is a weasel word!
docs/data/data-mapping/data-item-linking/item-linking-concepts.md|24 col 45| [from-write-good.Weasel] 'completely' is a weasel word!
docs/data/data-mapping/data-mapping-ui.md|65 col 131| [from-write-good.Passive] 'is indicated' may be passive voice. Use active voice if you can.
docs/data/data-mapping/data-mapping-ui.md|150 col 28| [from-write-good.Weasel] 'normally' is a weasel word!
docs/data/transforming-data.md|7 col 110| [from-write-good.Weasel] 'correctly' is a weasel word!
docs/data/transforming-data.md|9 col 123| [from-write-good.Passive] 'be processed' may be passive voice. Use active voice if you can.
docs/data/transforming-data.md|11 col 251| [from-write-good.Passive] 'was returned' may be passive voice. Use active voice if you can.
docs/data/transforming-data.md|22 col 114| [from-write-good.TooWordy] 'similar to' is too wordy.
docs/data/index.md|7 col 147| [from-write-good.TooWordy] 'However' is too wordy.
docs/data/index.md|33 col 114| [from-write-good.TooWordy] 'similar to' is too wordy.
docs/cloud-admin-dashboard.md|29 col 16| [from-microsoft.Adverbs] Consider removing 'regularly'.
docs/cloud-admin-dashboard.md|29 col 16| [from-write-good.Weasel] 'regularly' is a weasel word!
docs/try-it-out/index.md|10 col 39| [from-write-good.Weasel] 'Very' is a weasel word!
docs/try-it-out/index.md|10 col 39| [from-microsoft.Adverbs] Consider removing 'Very'.
docs/integrations/custom-operations.md|13 col 276| [from-write-good.TooWordy] 'additional' is too wordy.
docs/try-it-out/quickstart.md|6 col 7| [from-write-good.Weasel] 'very' is a weasel word!
docs/try-it-out/quickstart.md|6 col 7| [from-microsoft.Adverbs] Consider removing 'very'.
docs/try-it-out/longer-introduction.md|113 col 30| [from-write-good.TooWordy] 'similar to' is too wordy.
docs/integrations/creating-nodes/build/declarative-style-node.md|23 col 327| [from-write-good.TooWordy] 'implement' is too wordy.
docs/integrations/creating-nodes/build/declarative-style-node.md|136 col 10| [from-microsoft.Wordiness] Consider using 'some' instead of 'some of the'.
docs/integrations/creating-nodes/build/declarative-style-node.md|166 col 84| [from-write-good.TooWordy] 'type of' is too wordy.
docs/integrations/creating-nodes/build/declarative-style-node.md|292 col 35| [from-write-good.TooWordy] 'additional' is too wordy.
docs/integrations/creating-nodes/build/declarative-style-node.md|464 col 96| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/integrations/creating-nodes/build/reference/http-helpers.md|60 col 7| [from-write-good.Passive] 'is required' may be passive voice. Use active voice if you can.
docs/integrations/creating-nodes/build/reference/http-helpers.md|82 col 83| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/integrations/creating-nodes/build/reference/http-helpers.md|86 col 127| [from-write-good.Passive] 'was removed' may be passive voice. Use active voice if you can.
docs/integrations/creating-nodes/build/reference/http-helpers.md|88 col 4| [from-write-good.TooWordy] 'minimize' is too wordy.
docs/integrations/creating-nodes/plan/node-ui-design.md|13 col 181| [from-write-good.TooWordy] 'However' is too wordy.
docs/integrations/creating-nodes/plan/node-ui-design.md|37 col 225| [from-write-good.Weasel] 'usually' is a weasel word!
docs/integrations/creating-nodes/plan/node-ui-design.md|67 col 6| [from-write-good.Weasel] 'usually' is a weasel word!
docs/integrations/creating-nodes/plan/node-ui-design.md|101 col 28| [from-write-good.Passive] 'are required' may be passive voice. Use active voice if you can.
docs/integrations/creating-nodes/build/programmatic-style-node.md|67 col 75| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/integrations/creating-nodes/build/programmatic-style-node.md|145 col 10| [from-microsoft.Wordiness] Consider using 'some' instead of 'some of the'.
docs/integrations/creating-nodes/build/programmatic-style-node.md|169 col 84| [from-write-good.TooWordy] 'type of' is too wordy.
docs/integrations/creating-nodes/build/programmatic-style-node.md|173 col 67| [from-write-good.Weasel] 'usually' is a weasel word!
docs/integrations/creating-nodes/build/programmatic-style-node.md|227 col 35| [from-write-good.TooWordy] 'additional' is too wordy.
docs/integrations/creating-nodes/build/programmatic-style-node.md|333 col 27| [from-write-good.TooWordy] 'subsequent' is too wordy.
docs/integrations/creating-nodes/build/programmatic-style-node.md|478 col 102| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/integrations/creating-nodes/build/reference/node-versioning.md|55 col 82| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/integrations/creating-nodes/build/reference/node-versioning.md|60 col 83| [from-write-good.Weasel] 'usually' is a weasel word!
docs/integrations/creating-nodes/build/reference/node-file-structure.md|9 col 47| [from-write-good.Passive] 'is affected' may be passive voice. Use active voice if you can.
docs/integrations/creating-nodes/build/reference/node-file-structure.md|13 col 7| [from-write-good.Weasel] 'many' is a weasel word!
docs/integrations/creating-nodes/build/reference/node-file-structure.md|19 col 58| [from-write-good.Passive] 'is required' may be passive voice. Use active voice if you can.
docs/integrations/creating-nodes/build/reference/node-file-structure.md|31 col 133| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/integrations/creating-nodes/build/reference/node-file-structure.md|46 col 15| [from-write-good.Weasel] 'many' is a weasel word!
docs/integrations/creating-nodes/build/reference/node-codex-files.md|9 col 131| [from-write-good.Passive] 'be named' may be passive voice. Use active voice if you can.
docs/integrations/creating-nodes/build/reference/ui-elements.md|104 col 69| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/integrations/creating-nodes/build/reference/ui-elements.md|369 col 23| [from-write-good.TooWordy] 'evaluate' is too wordy.
docs/integrations/creating-nodes/build/reference/ui-elements.md|566 col 71| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/integrations/creating-nodes/build/reference/ui-elements.md|570 col 487| [from-write-good.TooWordy] 'validate' is too wordy.
docs/integrations/creating-nodes/build/reference/ui-elements.md|612 col 77| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/integrations/creating-nodes/build/reference/ui-elements.md|614 col 82| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/integrations/creating-nodes/build/reference/ui-elements.md|618 col 32| [from-write-good.TooWordy] 'implement' is too wordy.
docs/integrations/creating-nodes/build/reference/ui-elements.md|655 col 93| [from-write-good.TooWordy] 'implement' is too wordy.
docs/integrations/creating-nodes/build/reference/ui-elements.md|715 col 209| [from-write-good.TooWordy] 'additional' is too wordy.
docs/integrations/creating-nodes/build/reference/ui-elements.md|731 col 62| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/integrations/creating-nodes/build/reference/code-standards.md|11 col 53| [from-write-good.Weasel] 'many' is a weasel word!
docs/integrations/creating-nodes/build/reference/code-standards.md|97 col 266| [from-write-good.Passive] 'be loaded' may be passive voice. Use active voice if you can.
docs/integrations/creating-nodes/test/node-linter.md|44 col 134| [from-write-good.Passive] 'be turned' may be passive voice. Use active voice if you can.
docs/integrations/creating-nodes/build/reference/node-base-files.md|95 col 41| [from-write-good.Weasel] 'currently' is a weasel word!
docs/integrations/creating-nodes/build/reference/node-base-files.md|149 col 55| [from-write-good.Passive] 'is required' may be passive voice. Use active voice if you can.
docs/integrations/creating-nodes/build/reference/node-base-files.md|164 col 53| [from-write-good.Weasel] 'usually' is a weasel word!
docs/integrations/creating-nodes/build/reference/node-base-files.md|196 col 6| [from-write-good.TooWordy] 'Additional' is too wordy.
docs/integrations/creating-nodes/build/reference/node-base-files.md|232 col 200| [from-write-good.TooWordy] 'subsequent' is too wordy.
docs/integrations/creating-nodes/build/reference/node-base-files.md|351 col 268| [from-write-good.TooWordy] 'subsequent' is too wordy.
docs/integrations/builtin/credentials/linkedin.md|24 col 140| [from-microsoft.Terms] Prefer 'GB' over 'gb'.
docs/integrations/builtin/credentials/linkedin.md|33 col 138| [from-microsoft.We] Try to avoid using first-person plural like 'us'.
docs/integrations/builtin/credentials/surveymonkey.md|24 col 13| [from-microsoft.FirstPerson] Use first person (such as 'My') sparingly.
docs/integrations/builtin/credentials/surveymonkey.md|35 col 13| [from-microsoft.FirstPerson] Use first person (such as 'My') sparingly.
docs/integrations/builtin/credentials/twist.md|25 col 28| [from-microsoft.Ellipses] In general, don't use an ellipsis.
docs/integrations/builtin/credentials/twist.md|43 col 68| [from-microsoft.HeadingPunctuation] Don't use end punctuation in headings.
docs/integrations/builtin/credentials/twist.md|44 col 51| [from-write-good.TooWordy] 'However' is too wordy.
docs/integrations/builtin/credentials/twist.md|45 col 4| [from-microsoft.We] Try to avoid using first-person plural like 'We'.
docs/integrations/builtin/credentials/ssh.md|21 col 62| [from-microsoft.We] Try to avoid using first-person plural like 'we'.
docs/integrations/builtin/credentials/ssh.md|22 col 82| [from-microsoft.We] Try to avoid using first-person plural like 'we'.
docs/integrations/builtin/credentials/ssh.md|34 col 62| [from-microsoft.We] Try to avoid using first-person plural like 'we'.
docs/integrations/builtin/credentials/zendesk.md|70 col 11| [from-microsoft.FirstPerson] Use first person (such as ' I ') sparingly.
docs/integrations/builtin/credentials/zendesk.md|70 col 18| [from-microsoft.FirstPerson] Use first person (such as 'my') sparingly.
docs/integrations/builtin/credentials/zendesk.md|70 col 37| [from-microsoft.HeadingPunctuation] Don't use end punctuation in headings.
docs/integrations/builtin/credentials/discord.md|17 col 10| [from-write-good.TooWordy] 'type of' is too wordy.
docs/integrations/builtin/credentials/discord.md|19 col 23| [from-write-good.Passive] 'are added' may be passive voice. Use active voice if you can.
docs/integrations/builtin/credentials/discord.md|21 col 25| [from-write-good.Passive] 'are added' may be passive voice. Use active voice if you can.
docs/integrations/builtin/credentials/discord.md|21 col 162| [from-write-good.TooWordy] 'However' is too wordy.
docs/integrations/builtin/credentials/discord.md|21 col 354| [from-write-good.TooWordy] 'sufficient' is too wordy.
docs/integrations/builtin/credentials/quickbase.md|20 col 52| [from-microsoft.FirstPerson] Use first person (such as 'My') sparingly.
docs/integrations/builtin/credentials/servicenow.md|39 col 82| [from-write-good.Passive] 'be seen' may be passive voice. Use active voice if you can.
docs/integrations/builtin/credentials/servicenow.md|41 col 24| [from-write-good.TooWordy] 'finalize' is too wordy.
docs/integrations/builtin/credentials/rocketchat.md|22 col 13| [from-microsoft.FirstPerson] Use first person (such as 'My') sparingly.
docs/integrations/builtin/credentials/airtable.md|46 col 15| [from-write-good.Passive] 'be deprecated' may be passive voice. Use active voice if you can.
docs/integrations/builtin/credentials/cal.md|19 col 19| [from-write-good.Passive] 'are authenticated' may be passive voice. Use active voice if you can.
docs/integrations/builtin/credentials/cal.md|23 col 118| [from-write-good.Passive] 'be found' may be passive voice. Use active voice if you can.
docs/integrations/builtin/credentials/mattermost.md|34 col 67| [from-microsoft.HeadingPunctuation] Don't use end punctuation in headings.
docs/integrations/builtin/credentials/mattermost.md|44 col 27| [from-write-good.Passive] 'are generated' may be passive voice. Use active voice if you can.
docs/integrations/builtin/credentials/mattermost.md|44 col 76| [from-write-good.Passive] 'be enabled' may be passive voice. Use active voice if you can.
docs/integrations/builtin/credentials/mattermost.md|46 col 15| [from-write-good.TooWordy] 'additional' is too wordy.
docs/integrations/builtin/credentials/mailjet.md|23 col 30| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'Master'.
docs/integrations/builtin/credentials/xero.md|21 col 26| [from-write-good.Passive] 'is selected' may be passive voice. Use active voice if you can.
docs/integrations/builtin/credentials/bitwarden.md|23 col 15| [from-alex.Race] Consider using 'primary', 'hub', or 'reference' instead of 'master'.
docs/integrations/builtin/credentials/customerio.md|49 col 11| [from-microsoft.FirstPerson] Use first person (such as ' I ') sparingly.
docs/integrations/builtin/credentials/customerio.md|49 col 58| [from-microsoft.HeadingPunctuation] Don't use end punctuation in headings.
docs/integrations/builtin/credentials/ldap.md|26 col 47| [from-microsoft.We] Try to avoid using first-person plural like 'us'.
docs/integrations/builtin/credentials/ldap.md|27 col 35| [from-microsoft.We] Try to avoid using first-person plural like 'us'.
docs/integrations/builtin/credentials/google/oauth-generic.md|70 col 1| [from-write-good.Weasel] 'Many' is a weasel word!
docs/integrations/builtin/credentials/google/index.md|23 col 181| [from-write-good.Passive] 'is limited' may be passive voice. Use active voice if you can.