Update docs

Author: mlafeldt

README.md

@@ -204,32 +204,19 @@ You can adjust this behavior in a number of ways:
    cargo build --examples
    ```
 
-3. _Experimental:_ Setting `DUCKDB_DOWNLOAD_LIB=1` makes the build script download
-   prebuilt DuckDB binaries from the official DuckDB releases for the active `TARGET`.
-   This is the quickest way to use the official binaries without manually downloading
-   them, but the feature is still considered experimental.
-   The archives are cached in `target/duckdb-download/<target>/<version>` (or under
-   `CARGO_TARGET_DIR` if set) and that directory is added to the linker search path
-   automatically, including an rpath on Unix so runtime lookup works without
-   additional environment variables. The downloaded version always matches the
-   `libduckdb-sys` crate version.
+3. _Experimental:_ Setting `DUCKDB_DOWNLOAD_LIB=1` makes the build script download pre-built DuckDB binaries from GitHub Releases. This always links against the dynamic library in the archive (setting `DUCKDB_STATIC` has no effect), and it effectively automates the manual steps above. The archives are cached in `target/duckdb-download/<target>/<version>` and that directory is automatically added to the linker search path. The downloaded version always matches the `libduckdb-sys` crate version.
 
    ```shell
    DUCKDB_DOWNLOAD_LIB=1 cargo test
    ```
 
-   Supported `TARGET`s include `x86_64-unknown-linux-gnu`, `aarch64-unknown-linux-gnu`,
-   `x86_64-apple-darwin`, `aarch64-apple-darwin`, `x86_64-pc-windows-msvc`, and
-   `aarch64-pc-windows-msvc`.
-
 4. Installing the duckdb development packages will usually be all that is required, but
    the build helpers for [pkg-config](https://github.com/alexcrichton/pkg-config-rs)
    and [vcpkg](https://github.com/mcgoo/vcpkg-rs) have some additional configuration
    options. The default when using vcpkg is to dynamically link,
    which must be enabled by setting `VCPKGRS_DYNAMIC=1` environment variable before build.
-   When none of the options above are used, the build script falls back to this discovery
-   path and will emit the appropriate `cargo:rustc-link-lib` directives if DuckDB is found
-   on your system.
+
+When none of the options above are used, the build script falls back to this discovery path and will emit the appropriate `cargo:rustc-link-lib` directives if DuckDB is found on your system.
 
 ### ICU extension and the bundled feature