diff --git a/content/master/operations/operation.md b/content/master/operations/operation.md
index 305d1f54..051a180a 100644
--- a/content/master/operations/operation.md
+++ b/content/master/operations/operation.md
@@ -408,10 +408,15 @@ Operations emit Kubernetes events for important activities:
 
 ### Troubleshooting operations
 
-**Select operation status:**
+**Check operation status:**
 
 ```shell
 kubectl get operation my-operation -o wide
+```
+
+**View detailed information:**
+
+```shell
 kubectl describe operation my-operation
 ```
 
diff --git a/content/master/operations/watchoperation.md b/content/master/operations/watchoperation.md
index 6aeb5875..71db9064 100644
--- a/content/master/operations/watchoperation.md
+++ b/content/master/operations/watchoperation.md
@@ -115,13 +115,12 @@ spec:
 
 ## Resource injection
 
-When a WatchOperation creates an Operation, it automatically injects the 
-changed
 <!-- vale write-good.TooWordy = NO -->
-resource using the special requirement name 
-`ops.crossplane.io/watched-resource`.
+When a WatchOperation creates an Operation, it automatically injects the changed
+resource using the special requirement name
+`ops.crossplane.io/watched-resource`. Functions can access this resource without
+explicitly requesting it.
 <!-- vale write-good.TooWordy = YES -->
-Functions can access this resource without explicitly requesting it.
 
 For example, when a ConfigMap with label `validate: "true"` changes, the 
 WatchOperation creates an Operation like this:
@@ -498,10 +497,10 @@ kubectl get events --field-selector involvedObject.name=my-watchop
 
 ### Event handling
 
+<!-- vale write-good.TooWordy = NO -->
 1. **Implement event filtering** - Check generation, deletion timestamp, 
    and status conditions
    to avoid processing irrelevant changes
-<!-- vale write-good.TooWordy = NO -->
 1. **Monitor operation volume** - Popular resources can create numerous 
    Operations
 <!-- vale write-good.TooWordy = YES -->
@@ -597,4 +596,4 @@ operational considerations, see [Operation best practices]({{<ref "operation#bes
 
 - Learn about [Operation]({{<ref "operation">}}) for one-time operational tasks
 - Learn about [CronOperation]({{<ref "cronoperation">}}) for scheduled operations
-- [Get started with Operations]({{<ref "../get-started/get-started-with-operations">}}) to create your first reactive operation
\ No newline at end of file
+- [Get started with Operations]({{<ref "../get-started/get-started-with-operations">}}) to create your first reactive operation