(fixup) may -> can or might

Author: michaeltlombardi

dsc/docs-conceptual/dsc-3.0/concepts/enhanced-authoring.md

@@ -32,7 +32,7 @@ specific to VS Code that:
 >
 > These schemas are only for improving the authoring experience. If you try to validate the
 > configuration document or resource manifest with a tool that doesn't support the extended
-> vocabulary, the tool may raise an error.
+> vocabulary, the tool might raise an error.
 >
 > The enhanced schemas share the same source definition as the canonical schemas and validate the
 > data in the same way. However, they include non-canonical keywords. For maximum compatibility

dsc/docs-conceptual/dsc-3.0/concepts/resources/anatomy.md

@@ -50,7 +50,7 @@ At a minimum, the manifest must define:
   - A command to validate nested DSC Resources. This last option only applies to DSC group
     resources and DSC adapter resources.
 
-The manifest may define:
+The manifest can define:
 
 - The kind of resource the manifest describes: `adapter`, `group`, `importer`, or `resource`.
 
@@ -82,7 +82,7 @@ for each operation is independent.
 
 Command resources always require an executable file for DSC to run. The manifest doesn't need to be
 bundled with the executable. The executable can be any executable file, such as a binary
-application or a shell script. A resource may use different executables for different operations.
+application or a shell script. A resource can use different executables for different operations.
 
 For DSC to use an executable, it must be discoverable in the `PATH` environment variable. DSC calls
 the executable once per operation, using the exit code returned by the executable to determine if

dsc/docs-conceptual/dsc-3.0/concepts/resources/capabilities.md

@@ -113,7 +113,7 @@ For resources with the `delete` capability and the [_exist][07] canonical resour
   the resource when the desired state defines `_exist` as `false`.
 
 Resources with the `delete` capability that don't have the `_exist` canonical resource property
-must implement their **Set** operation to handle removing instances. DSC cannot infer existence
+must implement their **Set** operation to handle removing instances. DSC can't infer existence
 semantics without the `_exist` property.
 
 A command resource has this capability when it defines the [delete][14] property in its resource

dsc/docs-conceptual/dsc-3.0/concepts/resources/instances.md

@@ -6,7 +6,7 @@ and value is a different instance of the resource.
 
 Every command resource defines a [resource instance schema][01] that describes how to validate and
 manage an instance of the resource with a JSON Schema. [Adapter resources][02] implement the
-[Validate operation][03] to enable validating adapted resource instances, which may not have JSON
+[Validate operation][03] to enable validating adapted resource instances, which might not have JSON
 Schemas to describe their properties.
 
 If you specify an invalid definition for a resource instance, DSC raises an error before invoking

dsc/docs-conceptual/dsc-3.0/concepts/resources/kinds.md

@@ -11,7 +11,7 @@ For more information about how DSC determines resource kinds, see
 ## Adapter resources
 
 An adapter resource makes non-command resources available to DSC. They always have a `resources`
-property that takes an array of nested resource instances. Adapters may provide additional control
+property that takes an array of nested resource instances. Adapters can provide additional control
 over how the adapted resources are processed.
 
 For example, the `Microsoft.DSC/PowerShell` adapter enables you to use PowerShell Desired State

dsc/docs-conceptual/dsc-3.0/concepts/resources/operations.md

@@ -89,7 +89,7 @@ This operation is only available for [adapter resources][06].
 
 The **Validate** operation indicates whether an instance of the resource is validly defined.
 Command resources use their resource instance schema for validation. Adapter resources implement
-the **Validate** operation to enable DSC to validate adapted resources, which may not have a
+the **Validate** operation to enable DSC to validate adapted resources, which might not have a
 defined JSON Schema.
 
 DSC invokes the **Validate** operation on adapter resources when validating adapted resource

dsc/docs-conceptual/dsc-3.0/concepts/resources/overview.md

@@ -26,7 +26,7 @@ DSC supports several kinds of resources:
 - A resource defined with a resource manifest is a _command_ resource. DSC uses the manifest
   to determine how to invoke the resource and how to validate the resource instance properties.
 - A _group resource_ is a command resource with a `resources` property that takes an array of
-  resource instances and processes them. Group resources may apply special handling to their nested
+  resource instances and processes them. Group resources can apply special handling to their nested
   resource instances, like changing the user the resources run as.
 - An _adapter resource_ is a group resource that enables the use of non-command resources with DSC.
   For example, the `Microsoft.DSC/PowerShell` and `Microsoft.Windows/WindowsPowerShell` adapter
@@ -60,7 +60,7 @@ instance schema.
 
 Properties are optional by default. Resources can be invoked directly or declared in a
 configuration with only the properties that are relevant to the current task or purpose. You don't
-need to declare every property for an instance. Properties may have default values for their
+need to declare every property for an instance. Properties can have default values for their
 desired state.
 
 Most properties are one of the basic types:
@@ -75,7 +75,7 @@ Most properties are one of the basic types:
 Complex properties require the property value to be an object with defined subproperties. The
 subproperties can be basic or complex, but they're usually a basic type.
 
-Resources may define their properties as read-only or write-only:
+Resources can define their properties as read-only or write-only:
 
 - A _read-only resource property_ defines metadata about an instance that the resource can retrieve
   but that a user can't directly set. You can't specify read-only properties in the desired state

dsc/docs-conceptual/dsc-3.0/concepts/resources/properties.md

@@ -80,28 +80,28 @@ the property is a key property.
 
 ## Required resource properties
 
-When defining a resource instance, some properties may be required. An instance that doesn't
+When defining a resource instance, some properties might be required. An instance that doesn't
 define required properties is invalid. DSC raises a validation error before invoking the resource
 when required properties are missing.
 
-Properties may be _always_ required. DSC determines whether a resource property is a required
+Properties can be _always_ required. DSC determines whether a resource property is a required
 propety by examining the `required` keyword in the instance schema. If the instance schema defines
 the `required` keyword and the property name is included in the array of values for the keyword,
 the property is always required.
 
-Properties may be _conditionally_ required. Resources can conditionally require a property with the
+Properties can be _conditionally_ required. Resources can conditionally require a property with the
 `dependentRequires` keyword or other conditional keywords. For more information about conditionally
 applied subschemas, see
 [Conditional schema validation][01].
 
 ## Read-only resource properties
 
-Resources may define read-only properties to describe information about an instance that the
+Resources can define read-only properties to describe information about an instance that the
 resource can retrieve but not directly set. For example, file APIs don't generally allow a user to
 set the property describing the last time the file was modified.
 
 Generally, you should not include read-only properties when defining the desired state for an
-instance. Assertion resources that don't support the **Set** operation may include read-only
+instance. Assertion resources that don't support the **Set** operation can include read-only
 properties you can use for validating system state for conditional behavior.
 
 DSC determines whether a resource property is a read-only property by examining the property
@@ -110,7 +110,7 @@ subschema in the instance schema. If the subschema defines the `readOnly` keywor
 
 ## Write-only resource properties
 
-Resources may define write-only properties that affect how the resource behaves but that the
+Resources can define write-only properties that affect how the resource behaves but that the
 resource can't retrieve for the actual state of an instance. For example, a resource might support
 credentials for downloading a file, but won't return those credentials in the output.
 

dsc/docs-conceptual/dsc-3.0/glossary.md

@@ -8,9 +8,9 @@ ms.date: 03/18/2025
 
 # Glossary: Desired State Configuration
 
-Microsoft Desired State Configuration (DSC) uses several terms that may have different definitions
-elsewhere. This document lists the terms, their meanings, and shows how they're formatted in the
-documentation.
+Microsoft Desired State Configuration (DSC) uses several terms that might have different
+definitions elsewhere. This document lists the terms, their meanings, and shows how they're
+formatted in the documentation.
 
 <!-- markdownlint-disable MD028 MD036 MD024 -->
 
@@ -27,7 +27,7 @@ The JSON or YAML data that defines a list of resource instances and their desire
 
 #### Examples
 
-> A DSC Configuration Document may be formatted as JSON or YAML.
+> A DSC Configuration Document can be formatted as JSON or YAML.
 
 > Define the `scope` variable in the document as `machine`.
 
@@ -52,7 +52,7 @@ resources.
 
 ### DSC resource instance
 
-A single item configured by a DSC resource. A resource may manage any number of instances. Each
+A single item configured by a DSC resource. A resource can manage any number of instances. Each
 instance uniquely represents an item, like a specific file or a software package.
 
 A DSC configuration document defines the desired state for one or more instances.
@@ -87,7 +87,7 @@ determine how to invoke the resource and how to validate the resource instance p
 ### DSC group resource
 
 A _group resource_ is a resource with a `resources` property that takes an array of resource
-instances and processes them. Group resources may apply special handling to their nested resource
+instances and processes them. Group resources can apply special handling to their nested resource
 instances, like changing the user the resources run as.
 
 #### Guidelines
@@ -164,7 +164,7 @@ resource). PSDSC resources are further distinguished by their implementation:
 - **Subsequent mentions:** PSDSC resources.
 - When discussing a specific type of PowerShell resource, always specify the type prefix, like
   _class-based PSDSC resources_.
-- The PSDSC prefix may be omitted when the context is clearly or only about PowerShell DSC
+- The PSDSC prefix can be omitted when the context is clearly or only about PowerShell DSC
   resources, like a tutorial for authoring a class-based resource.
 
 <!-- vale alex.Condescending = YES -->
@@ -181,7 +181,7 @@ resource). PSDSC resources are further distinguished by their implementation:
 ### DSC Resource manifest
 
 The data file that defines the metadata and implementation of a command-based resource. A resource
-manifest may be authored in either JSON or YAML.
+manifest can be authored in either JSON or YAML.
 
 #### Guidelines
 
@@ -270,7 +270,7 @@ properties.
 ### Key resource properties
 
 The key properties of a resource uniquely identify an instance of the resource. No two instances of
-a resource in a configuration may have identical key properties.
+a resource in a configuration can have identical key properties.
 
 If two instances have the same key properties but different values for the other properties, the
 configuration will never be in the desired state and DSC will reconfigure the instance during every
@@ -330,7 +330,7 @@ properties, see [DSC canonical properties][01]
 ### Read-only resource properties
 
 Read-only resource properties of a resource describe non-configurable information about an instance
-that the resource returns. This may include metadata like the last time a file was modified or the
+that the resource returns. This can include metadata like the last time a file was modified or the
 latest available version of a package.
 
 Resources indicate which properties are read-only in their instance schema by defining the

dsc/docs-conceptual/dsc-3.0/reference/cli/dsc.md

@@ -89,7 +89,7 @@ set to any value in the list, DSC emits messages at that level and above.
 > [!WARNING]
 > The `trace` level output emits all JSON input/output that DSC processes during execution. DSC
 > doesn't sanitize the JSON before emitting it. This trace level is only intended for developer
-> use. Never redirect `trace` level output to storage as it may contain sensitive information.
+> use. Never redirect `trace` level output to storage as it might contain sensitive information.
 
 For example, when the log level is `debug`, DSC emits messages for every log level except `trace`.
 When the log level is `error`, DSC only emits error messages. DSC ignores every message with a