Correct docs/spec wording and align Endpoint prevention message strings

deploy/helm/elastic-agent/CONTRIBUTING.md

@@ -57,11 +57,11 @@ helm upgrade elastic-agent . -f your-values.yaml --set kubernetes.enabled=false
 
 The README.md was originally generated using [helm-docs](https://github.com/norwoodj/helm-docs).
 However, it has diverged from the auto-generated version since.
-`helm-docs` is still usefull to can pick up changes to the `values.yaml` and
+`helm-docs` is still useful for picking up changes to the `values.yaml` and
 format them as the others. However, running it will completely override the
 README.md.
 You might use `helm-docs` to render the changes you made to `values.yaml`. Then,
-find you changes, copy it, restore the README.md and manually add your changes.
+find your changes, copy them, restore the README.md, and manually add your changes.
 
 
 ### Adding New Values Documentation

docs/architecture.md

@@ -38,8 +38,8 @@ The first stage of the process is to convert the YAML policy into an internal ab
 ### 2 Composable Providers & Variable Substitution
 After conversion of the policy into the AST the resulting AST is used to process the variables provided by the provider system inside the Elastic Agent. This substitutes any variables with values given by the providers or uses default variable values if the provider does not provide a value for the variable reference.
 ### 3 Apply Conditions
-The next stage of the policy's journey is to apply conditions. Applying conditions can result in parts of the policy being removed. This is used by many integrations to change the behavior based on variables that come from provides. (e.g. removing the winlog input on non-Windows hosts for the system integration).
-Additonal documentation for the specs files can be found in [component-specs.md](compoonent-specs.md).
+The next stage of the policy's journey is to apply conditions. Applying conditions can result in parts of the policy being removed. This is used by many integrations to change the behavior based on variables that come from providers. (e.g. removing the winlog input on non-Windows hosts for the system integration).
+Additional documentation for the specs files can be found in [component-specs.md](component-specs.md).
 ### 4 Compute Model
 The final stage of the policy’s journey is to compute the components and units model that represents the expected state of the running Elastic Agent environment. Using the input specifications that each component defines in the Elastic Agent component directory, the Elastic Agent computes a model. That model can be different based on the platform that the Elastic Agent is running on because of specification settings defined in a component’s specification.
 

docs/hybrid-agent-beats-receivers.md

@@ -52,12 +52,12 @@ for the specific input. For example to run the `filestream` and
 agent:
   internal:
     runtime:
-      default: process # Run all beats and inputs as sub-processes unless overridden below or by harcoded defaults.
+      default: process # Run all beats and inputs as sub-processes unless overridden below or by hardcoded defaults.
       filebeat:
-        default: process # Run all Filebeat inputs as sub-processe unless overidden individually or by harcoded defaults.
+        default: process # Run all Filebeat inputs as sub-processes unless overridden individually or by hardcoded defaults.
         filestream: otel # Run the Filebeat filestream input as a beat receiver.
       metricbeat:
-        default: process # Run all Metricbeat inputs as sub-processe unless overidden individually or by harcoded defaults.
+        default: process # Run all Metricbeat inputs as sub-processes unless overridden individually or by hardcoded defaults.
         system/metrics: otel # Run the Metricbeat system/metrics input as a beat receiver.
 inputs:
   - id: system-metrics-receiver

testing/integration/ess/endpoint_security_test.go

@@ -827,7 +827,7 @@ func TestEndpointSecurityNonDefaultBasePath(t *testing.T) {
 		}
 		for _, c := range state.Components {
 			if strings.Contains(c.Message,
-				"Elastic Defend requires Elastic Agent be installed at the default installation path") {
+				"Elastic Defend requires Elastic Agent to be installed at the default installation path") {
 				return true
 			}
 		}
@@ -886,9 +886,9 @@ func TestEndpointSecurityUnprivileged(t *testing.T) {
 
 	c := fixture.Client()
 
-	errMsg := "Elastic Defend requires Elastic Agent be running as root"
+	errMsg := "Elastic Defend requires Elastic Agent to be running as root"
 	if runtime.GOOS == define.Windows {
-		errMsg = "Elastic Defend requires Elastic Agent be running as Administrator or SYSTEM"
+		errMsg = "Elastic Defend requires Elastic Agent to be running as Administrator or SYSTEM"
 	}
 	require.Eventually(t, func() bool {
 		err := c.Connect(ctx)