Content bug: inconsistent/incomplete descriptions of Promises as parameters

[foolip]

What page(s) did you find the problem on?

Compare the descriptions of parameters here:
https://developer.mozilla.org/en-US/docs/Web/API/PaymentRequest/show
https://developer.mozilla.org/en-US/docs/Web/API/PaymentRequestUpdateEvent/updateWith

What is the problem?

PaymentRequest's show() method is documented as taking a promise, while PaymentRequestUpdateEvent's updateWith() method is documented as taking an object. Actually, the two both accept the same kind of parameter, and because of the way that promises work, one can pass either an object directly or a promise that resolves to an object.

What did you expect to see?

A consistent style that makes it clear what can be used as the argument.

Promises as parameters is not very common on the web platform, but there are other cases that also have a mix of styles:

• https://developer.mozilla.org/en-US/docs/Web/API/PaymentRequestEvent/respondWith (also incorrectly says the PaymentResponse interface instead of the PaymentHandlerResponse dictionary)
• https://developer.mozilla.org/en-US/docs/Web/API/ExtendableEvent/waitUntil (no issue here because the promise can resolve to anything)
• https://developer.mozilla.org/en-US/docs/Web/API/FetchEvent/respondWith (correctly says "Response or a Promise that resolves to a Response")
• https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WebAssembly/compileStreaming (correctly says "Response object or a promise that will fulfill with one")