Fix CHANGELOG: SET overwrites GET parameters, not POST

Author: lovasoa

CHANGELOG.md

@@ -6,10 +6,10 @@
      - **What changed**: Previously, `$x` would return a POST parameter value if no GET parameter named `x` existed.
      - **Fix**: Replace `$x` with `:x` when you need to access form field values.
      - **Example**: Change `SELECT $username` to `SELECT :username` when reading form submissions.
-   - **BREAKING**: `SET $name` no longer overwrites POST parameters when a POST parameter with the same name exists.
-     - **What changed**: `SET $name = 'value'` would previously overwrite the POST parameter `:name`. Now it creates an independent SET variable that shadows the POST parameter.
-     - **Fix**: Either rename your SET variable, or use `:name` to access the original POST value if needed.
-     - **Example**: If your form has a field named `name`, and you do `SET $name = 'modified'`, then `$name` will be 'modified' but `:name` will still contain the form value.
+   - **BREAKING**: `SET $name` no longer overwrites GET (URL) parameters when a URL parameter with the same name exists.
+     - **What changed**: `SET $name = 'value'` would previously overwrite the URL parameter `$name`. Now it creates an independent SET variable that shadows the URL parameter.
+     - **Fix**: This is generally the desired behavior. If you need to access the original URL parameter after setting a variable with the same name, use `sqlpage.variables('get')` to access it.
+     - **Example**: If your URL is `page.sql?name=john`, and you do `SET $name = 'modified'`, then `$name` will be 'modified'. The original URL parameter is still accessible via `sqlpage.variables('get')` but not via `$name` anymore.
    - **New behavior**: Variable lookup now follows this precedence:
      - `$variable` checks SET variables first, then URL parameters
      - `:variable` checks SET variables first, then POST parameters