DoCurlAsync with only one ConfigureAwait

BynderCurlConfigureAwait-v2.cs

public async Task<string> DoCurlAsync()
{
    using (var httpClient = new HttpClient())
    using (var httpResonse = await httpClient.GetAsync("https://www.bynder.com").ConfigureAwait(false))
    {
        return await httpResonse.Content.ReadAsStringAsync();
    }
}

In .NET, as Simon Timms described in his article, you have to be careful when using the HTTPClient class.
Continuous instantiation and disposal of the HTTPClient object may create a socket exhaustion on your machine and affect performance.
Consider reusing the HTTPClient object throughout your calls for better performance.

https://aspnetmonsters.com/2016/08/2016-08-27-httpclientwrong/
https://ankitvijay.net/2016/09/25/dispose-httpclient-or-have-a-static-instance/

Actually @JoanM you are incorrect.
Using ConfigureAwait(false) is an anti pattern.
If your application is x async methods deep, you would need to add ConfigureAwait(false) to each and every awaitable down the call stack; otherwise you risk using a method incorrectly sooner or later.