Move policy property details to settings/update.md to avoid duplication

Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>

Author: Copilot

Website/docs/settings/update.md

@@ -14,7 +14,22 @@ Check for new program versions on GitHub when the application is launched.
 
 :::info System-Wide Policy
 
-This setting can be controlled by administrators using a system-wide policy. See [System-Wide Policies](../system-wide-policies.md) for more information on how to configure the `Update_CheckForUpdatesAtStartup` policy.
+This setting can be controlled by administrators using a system-wide policy. See [System-Wide Policies](../system-wide-policies.md) for more information.
+
+**Policy Property:** `Update_CheckForUpdatesAtStartup`
+
+**Values:**
+- `true` - Force enable automatic update checks at startup for all users
+- `false` - Force disable automatic update checks at startup for all users
+- Omit the property - Allow users to control this setting themselves
+
+**Example:**
+
+```json
+{
+  "Update_CheckForUpdatesAtStartup": false
+}
+```
 
 :::
 

Website/docs/system-wide-policies.md

@@ -49,21 +49,6 @@ The `config.json` file uses a simple JSON structure to define policy values. An
 
 :::
 
-## Available Policies
-
-### Update_CheckForUpdatesAtStartup
-
-Controls whether the application checks for updates at startup for all users.
-
-**Type:** `Boolean` (true/false)
-
-**Default:** Not set (users control this setting)
-
-**Values:**
-- `true` - Force enable automatic update checks at startup for all users
-- `false` - Force disable automatic update checks at startup for all users
-- Omit the property - Allow users to control this setting themselves
-
 ## Deployment
 
 For enterprise deployments:
@@ -105,7 +90,7 @@ Ensure the `config.json` file has appropriate permissions so that regular users
 - Check the application logs for any error messages related to policy loading
 
 **Policy values not showing in UI:**
-- Ensure the property name matches exactly: `Update_CheckForUpdatesAtStartup`
+- Ensure the property name matches exactly (see the corresponding setting's documentation for the property name)
 - Verify the value is a boolean (`true` or `false`), not a string (`"true"` or `"false"`)
 - Check that there are no syntax errors in the JSON file