Update troubleshoot/observability/apm-agent-dotnet/apm-net-agent.md

Co-authored-by: Benjamin Ironside Goldstein <[email protected]>

Author: stevejgordon

troubleshoot/observability/apm-agent-dotnet/apm-net-agent.md

@@ -188,7 +188,7 @@ an outside party to control what transactions are recorded through the sampled f
 To control the context propagation behaviour, we have a [trace continuation strategy](apm-agent-dotnet://reference/config-http.md#config-trace-continuation-strategy) option. Choose either `restart` or `restart_external`. `restart` will ignore
 the sampling flag on all requests and always include a transaction for the trace. `restart_external` is similar,
 however it uses an extra header to detect if the calling service was instrumented by an Elastic APM agent. If so,
-we honour the sampling flag; if not (i.e. an external request), we force the trace to be sampled.
+it honors the sampling flag; if not (such as for an external request), it forces the trace to be sampled.
 
 
 ## Following error appears in logs: `The singleton APM agent has already been instantiated and can no longer be configured.` [double-agent-initialization-log]