docs: fix minor issues in profiles and manifests docs (apache#4007)

Author: kentkwu

docs/source/format/connection_profiles.rst

@@ -193,9 +193,12 @@ When using a profile name (not an absolute path), the driver manager searches fo
 1. **Additional Search Paths** (if configured via ``AdbcDriverManagerDatabaseSetAdditionalSearchPathList()``)
 2. **ADBC_PROFILE_PATH** environment variable (colon-separated on Unix, semicolon-separated on Windows)
 3. **Conda Environment** (if built with Conda support and ``CONDA_PREFIX`` is set):
+
    - ``$CONDA_PREFIX/etc/adbc/profiles/``
+
 4. **User Configuration Directory**:
-   - Linux: ``~/.config/adbc/profiles/``
+
+   - Linux: ``$XDG_CONFIG_HOME/adbc/profiles`` if set, else ``~/.config/adbc/profiles/``
    - macOS: ``~/Library/Application Support/ADBC/Profiles/``
    - Windows: ``%LOCALAPPDATA%\ADBC\Profiles\``
 
@@ -433,7 +436,7 @@ Store credentials separately from code:
 
    [options]
    adbc.snowflake.sql.account = "mycompany"
-   adbc.snowflake.sql.auth_token = "env_var(SNOWFLAKE_TOKEN)"
+   adbc.snowflake.sql.auth_token = "{{ env_var(SNOWFLAKE_TOKEN) }}"
 
 Then set ``SNOWFLAKE_TOKEN`` via environment variable, secrets manager, or configuration service.
 

docs/source/format/driver_manifests.rst

@@ -499,7 +499,7 @@ would happen for ODBC drivers. The search for a manifest on Windows would be the
      * ``entrypoint`` - the entrypoint to use for the driver if a non-default entrypoint is needed
      * ``driver`` - the path to the driver shared library
 
-   * If no registry key is found, then the directory ``%LOCAL_APPDATA%\ADBC\Drivers`` is searched
+   * If no registry key is found, then the directory ``%LOCALAPPDATA%\ADBC\Drivers`` is searched
 
 #. If the ``LOAD_FLAG_SEARCH_SYSTEM`` load option is set, the driver manager will search for a system-level configuration