Server Requirements: SS_PROTECTED_ASSETS_PATH="../.protected/" now resolves outside the project root

Both branches (en/00_Getting_Started/00_Server_Requirements.md, branch 5 line 142, branch 6 line 127) show:

# This will be inside your project root, along-side the public/ directory
SS_PROTECTED_ASSETS_PATH="../.protected/"

Since silverstripe/assets 3.2.2 (silverstripe/silverstripe-assets#713, fixing #706), ProtectedAssetAdapter::findRoot() passes the env value through AssetAdapter::findRoot(), which resolves a leading ../ to dirname(BASE_PATH). So on current CMS 6 this example ends up one level above the project root, not inside it. Before 3.2.2 the raw value was used, which under PHP-FPM (cwd = public/) happened to land in the project root, matching the comment.

I think the CMS 6 example could use ./.protected/ (resolved against BASE_PATH), or keep ../ and update the comment. I'm less sure what the CMS 5 page should say, since assets 2.x still uses the raw value there. It may be worth a short note, as upgrading can quietly move the protected store.

Start with en/00_Getting_Started/00_Server_Requirements.md, checking branch 5 line 142 and branch 6 line 127. Compare the documented path behavior for CMS 5/assets 2.x and CMS 6/assets 3.2.2, including the linked silverstripe-assets changes. Done means the examples and comments accurately describe the resolved location and warn about any upgrade-related move.