Building and Securing Web APIs with ASP.NET Core 3.0

Regarding curl 415 error. I am running it on Windows 10, with latest patches. Firewall off.
Yes I used the lines verbatim and include the header definition. Just ran the PUT test again as follows.
Tried to update to latest cUrl too.
Looks like curl gets confused when it is parsing the cmdline as it thinks term, JWT and definition are hosts. I have tried retyping all the " and ’ characters.

C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise>curl --insecure --request PUT --url https://localhost:5001/api/glossary --header 'content-type: application/json'  --data '{ "term": "JWT", "definition": "An open, industry standard RFC 7519 method for representing claims securely between two parties. Auth0 uses JWT format for ID Tokens."}'
{"type":"https://tools.ietf.org/html/rfc7231#section-6.5.13","title":"Unsupported Media Type","status":415,"traceId":"|2f09b40b-4753ea38bf3e6390."}curl: (6) Could not resolve host: application
curl: (6) Could not resolve host: term
curl: (6) Could not resolve host: JWT,
curl: (6) Could not resolve host: definition
curl: (3) [globbing] unmatched close brace/bracket in column 134

C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise>curl -V
curl 7.55.1 (Windows) libcurl/7.55.1 WinSSL
Release-Date: [unreleased]
Protocols: dict file ftp ftps http https imap imaps pop3 pop3s smtp smtps telnet tftp
Features: AsynchDNS IPv6 Largefile SSPI Kerberos SPNEGO NTLM SSL

C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise>

I have tried to guess a number of different other ways to reorder the cmd line or remove spaces, but curl is not happy and always returns 415.