What feature or product is affected?

REST API

What is the new or expected behavior?

use HTTP/2 instead of HTTP/1.1

How is the old or inaccurate behavior currently documented?

The REST API examples should use HTTP/2 instead of HTTP/1.1

For example, in this code snippet,

> HTTP/1.1 200 OK

If you command a lane change under 45mph, nothing will happen. It it should be clear to the user that no lane change can be done because the speed is too low.

Perhaps instead of the message "Steer Left to Start Lane Change" that appears above 45mph something like "Speed too low for lane change"

Which Category is your question related to?
API

Amplify CLI Version
4.39.0

What AWS Services are you utilizing?
API, Auth, Function

Provide additional details e.g. code snippets
I'm trying to configure an HTTP resolver to call a step function. The url needs the correct aws region. I know you can pass the environment like so ${env} but I couldn't find anything in t

After ethereum/solidity#10737 we should be able to replace nearly all non-range-based for loops by range-based loops using appropriate ranges.