Improve exception handling and documentation structure

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

Author: Copilot

Source/NETworkManager.Settings/SettingsManager.cs

@@ -92,14 +92,18 @@ public static string GetSettingsFolderLocation()
                 // Validate that the path doesn't contain invalid characters
                 try
                 {
-                    // This will throw if the path contains invalid characters
+                    // This will throw ArgumentException or NotSupportedException if the path contains invalid characters
                     _ = Path.GetFullPath(policyPath);
                     return policyPath;
                 }
-                catch (Exception ex)
+                catch (ArgumentException ex)
                 {
                     Log.Error($"Policy-provided SettingsFolderLocation contains invalid characters: {policyPath}. Falling back to default location.", ex);
                 }
+                catch (NotSupportedException ex)
+                {
+                    Log.Error($"Policy-provided SettingsFolderLocation format is not supported: {policyPath}. Falling back to default location.", ex);
+                }
             }
         }
 

Website/docs/system-wide-policies.md

@@ -32,7 +32,7 @@ The `config.json` file uses a simple JSON structure to define policy values. An
 ```
 
 
-**Example:**
+**Example with available policies:**
 
 ```json
 {
@@ -41,6 +41,8 @@ The `config.json` file uses a simple JSON structure to define policy values. An
 }
 ```
 
+For a complete list of available policies, see the [Available Policies](#available-policies) section below.
+
 Property names generally follow the pattern `Section_SettingName` (see each setting's documentation). Ensure values use the correct JSON type (boolean, string, number, etc.).
 
 :::note