From 5792ad9dcbadbd4ed9e42fb09d6605dde1bf270b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Serge=20Crois=C3=A9?= Date: Fri, 17 Jan 2025 19:39:10 +0100 Subject: [PATCH] Fix: contributing.md spelling (#10307) - technology - command line --- Documentation/contributing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/contributing.md b/Documentation/contributing.md index 9024fe1c5ae..5540946322e 100644 --- a/Documentation/contributing.md +++ b/Documentation/contributing.md @@ -16,7 +16,7 @@ Project maintainers will consider changes that improve the product or fix known Maintainers will not merge changes that have narrowly-defined benefits due to compatibility risk or complexity added to the product. We may revert changes if they are found to be breaking. -Most .NET Core components are cross-platform and we appreciate contributions that either improve their feature set in a given environment or that add support for a new environment. We will typically not accept contributions that implement support for an OS-specific technolology on another operating system. We also do not intend to accept contributions that provide cross-platform implementations for Windows Forms or WPF. +Most .NET Core components are cross-platform and we appreciate contributions that either improve their feature set in a given environment or that add support for a new environment. We will typically not accept contributions that implement support for an OS-specific technology on another operating system. We also do not intend to accept contributions that provide cross-platform implementations for Windows Forms or WPF. Contributions must also satisfy the [acceptance criteria](acceptance_criteria.md) to learn how to develop changes for this repo.as well as other published guidelines defined in this document. @@ -24,7 +24,7 @@ Contributions must also satisfy the [acceptance criteria](acceptance_criteria.md We will consider code-formatting improvements that are identified by running code analyzers. -Our CodeAnalysis rules are not enabled by default. These can be enabled by setting the MSBuild property `EnableAnalyzers=true` (in commandline, it is set as `/p:EnableAnalyzers=true`). +Our CodeAnalysis rules are not enabled by default. These can be enabled by setting the MSBuild property `EnableAnalyzers=true` (in command line, it is set as `/p:EnableAnalyzers=true`). The code analyzer would likely recommend changes that can result in changes to the generated IL. In general, we prefer code-formatting PR's to be limited to changes that do not have any impact on the IL - these are easier to review and approve and do not require additional testing.