fix: remove outdated screenshot (#22322)

<!--Delete sections as needed -->

## Description

Does what it says on the tin

## Related issues or tickets

<!-- Related issues, pull requests, or Jira tickets -->

## Reviews

<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->

- [ ] Technical review
- [ ] Editorial review
- [ ] Product review

content/manuals/security/for-admins/hardened-desktop/settings-management/_index.md

@@ -74,8 +74,6 @@ Enforced settings appear grayed out in Docker Desktop. They can't be edited via
 
 In addition, if Enhanced Container Isolation is enforced, developers can't use privileged containers or similar techniques to modify enforced settings within the Docker Desktop Linux VM. For example, they can't reconfigure proxy and networking, or Docker Engine.
 
-![Proxy settings grayed out](/assets/images/grayed-setting.png)
-
 ## What's next?
 
 - [Configure Settings Management with a `.json` file](configure-json-file.md)

content/manuals/security/for-admins/hardened-desktop/settings-management/configure-json-file.md

@@ -282,6 +282,4 @@ For settings to take effect:
 
 So as not to disrupt your developers' workflow, Docker doesn't automatically mandate that developers re-launch and re-authenticate once a change has been made.
 
-In Docker Desktop, developers see the relevant settings grayed out and the message **Locked by your administrator**.
-
-![Proxy settings grayed out with Settings Management](/assets/images/grayed-setting.png)
+In Docker Desktop, developers see the relevant settings grayed out.