more warnings

Author: BillWagner

docs/csharp/fundamentals/null-safety/common-tasks/resolve-warnings.md

@@ -48,7 +48,7 @@ The fix is usually a *guard clause*. A *guard clause* is a check at the top of a
 
 The property pattern `{ Length: > 0 }` matches only when `message` is non-null *and* its `Length` property is greater than zero, so the compiler treats `message` as *not-null* inside the `if` block. A simpler `is not null` test produces the same null-state narrowing without inspecting any properties.
 
-For an in-depth tour of the operators, see [Null operators](null-operators.md).
+For an in-depth tour of the operators, see [Null operators](../null-operators.md).
 
 ## Adjust annotations
 
@@ -133,8 +133,8 @@ To plan a migration that progressively enables nullable reference types in an ex
 
 ## Related content
 
-- [Nullable reference types](nullable-reference-types.md)
-- [Null operators](null-operators.md)
+- [Nullable reference types](../nullable-reference-types.md)
+- [Null operators](../null-operators.md)
 - [Nullable migration strategies](../../../advanced-topics/update-applications/nullable-migration-strategies.md)
 - [Nullable static analysis attributes](../../../language-reference/attributes/nullable-analysis.md)
 - [Resolve nullable warnings (compiler reference)](../../../language-reference/compiler-messages/nullable-warnings.md)