edits

Author: travisamartin

content/nginx-one/workshops/lab5/upgrade-nginx-plus-to-latest-version.md

@@ -75,7 +75,7 @@ Make sure you have:
        restart: always
    ```
 
-   > Tip: If you use VS Code, highlight lines 74–95 and press `Ctrl` + `/` to uncomment them.
+   {{< call-out "note" "Tip" "" >}} If you use VS Code, highlight lines 74–95 and press `Ctrl` + `/` to uncomment them. {{< /call-out >}}
 
 3. Restart your containers:
 
@@ -88,7 +88,7 @@ Make sure you have:
 6. Select that instance and verify it runs the latest versions of NGINX Plus and NGINX Agent.
 7. The `$NAME-plus4` container was added to the `$NAME-sync-group` config sync group and inherited the shared config.  
 
-   > **Tip:** Because new containers in a sync group automatically pick up the shared config, you get a consistent, tested setup across versions. You can shift traffic to the new container one at a time for a safer, zero-downtime upgrade, and avoid any manual copy-and-paste steps.
+   {{< call-out "note" "Tip" "" >}} Because new containers in a sync group automatically pick up the shared config, you get a consistent, tested setup across versions. You can shift traffic to the new container one at a time for a safer, zero-downtime upgrade, and avoid any manual copy-and-paste steps. {{< /call-out >}}
 
 ### Exercise A2: Delete unavailable containers
 
@@ -98,7 +98,7 @@ When you recreate containers, they re-register in the NGINX One Console. Use the
 2. Select **Add filter > Availability > Unavailable**.
 3. Check the boxes next to the unavailable hosts.
 4. Select **Delete selected**, then confirm.
-5. Remove the filter to view the full list again.
+5. Remove the filter: Hover over the **Availability is Unavailable** filter tag, then select **X** to clear it and show all instances again.
 
 <span style="display: inline-block;">
 {{< img src="nginx-one/images/unavailable-instances.png"