API doesn't agree on builds_enabled vs. jobs_enabled

Summary

Documentation and JSON response from the API only use jobs_enabled while the API seems to only accept builds_enabled as a parameter.

Steps to reproduce

curl --request PUT --header "PRIVATE-TOKEN: ${PRIVATE_TOKEN}" "https://gitlab.com/api/v4/projects/${PROJECT_ID}?jobs_enabled=false"

What is the current bug behavior?

{"error":"name, description, issues_enabled, merge_requests_enabled, wiki_enabled, builds_enabled, snippets_enabled, shared_runners_enabled, container_registry_enabled, lfs_enabled, visibility, public_builds, request_access_enabled, only_allow_merge_if_pipeline_succeeds, only_allow_merge_if_all_discussions_are_resolved, path, default_branch, repository_storage, approvals_before_merge are missing, at least one parameter must be provided"}

What is the expected correct behavior?

What happens if I use builds_enabled instead:

curl --request PUT --header "PRIVATE-TOKEN: ${PRIVATE_TOKEN}" "https://gitlab.com/api/v4/projects/${PROJECT_ID}?builds_enabled=false" | grep --only-matching --extended-regexp '"(builds_enabled|jobs_enabled)"[^,]+'

"jobs_enabled":false