Skip to content

Commit f9f604b

Browse files
committed
fixed link issues
1 parent 58b2129 commit f9f604b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/automation/troubleshoot/update-management.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,13 +33,13 @@ Superseded updates are not being correctly indicated as declined so that they ca
3333

3434
When a superseded update becomes 100 percent not applicable, you should change the approval state of that update to **Declined**. To do this for all your updates:
3535

36-
1. In the Automation Account, select **Update Management** to view machine status. See [View update assessments](manage-update-multi.md#view-an-update-assessment).
36+
1. In the Automation Account, select **Update Management** to view machine status. See [View update assessments](../manage-update-multi.md#view-an-update-assessment).
3737

3838
2. Check the superseded update to make sure that it is 100 percent not applicable.
3939

4040
3. Mark the update as declined unless you have a question about the update.
4141

42-
4. Select Computers and, in the Compliance column, force a rescan for compliance. See [Manage updates for multiple machines](manage-update-multi.md).
42+
4. Select Computers and, in the Compliance column, force a rescan for compliance. See [Manage updates for multiple machines](../manage-update-multi.md).
4343

4444
5. Repeat the steps above for other superseded updates.
4545

0 commit comments

Comments
 (0)