And weirder than that it’s not Amazon’s cut of the developer’s ‘revenue’ either - since the developer was never getting it in the first place - it’s their cut of the sale price, or the combined revenue, not the developer’s revenue.
2) And no: developer "revenue" is the full cost of the receipt, and then a cost of their doing business is the cut taken by the platform, which decreases their resulting "income". The word "revenue" specifically is a number from which you deduct costs to obtain "income".
Now, that said, one can actually use that construction to argue that the store is then having revenue, and giving a royalty to the developer or something, and in fact my store did something where I sometimes modeled it as a retail storefront of licenses I purchased wholesale, but these are just not normal models for how the word "cut" is then applied: most people reasonably--and I think correctly--believe that the user bought something from the developer, with the store acting merely as a middleman payment processor charging a "fee" or taking a "commission" off of every sale (and I am pretty sure at least Google even models it directly in that way in its reports; there are a ton of advantages to the store to doing that, and I think even Apple sometimes reaches for this model).
From such standpoint, and to look at this using descriptive linguistics, you simply don't ever see anyone say "Apple recently increased the cut of smaller developer's from 70% to 85%": every single headline I've seen says "Apple recently decreased their cut from smaller developers from 30% to 15%".
To me it's because in my mind "Amazon" is the person taking a "cut".
We never say "developers take 70% cut of the app store revenue", because developers don't "take a cut", they sell, and amazon takes a cut of their sale.
Still, I agree, the title is ambiguous.
Amazon to reduce its cut of dev revenue from 30% to 20% with 10% in AWS Credit
or
Amazon to reduce its cut of dev revenue from 30% to 20% plus 10% in AWS Credit