The page Mitigate Performance Issues with PSA Replica Set stated:

If one data-bearing node goes down, the other node becomes the primary. Writes with w:1 continue to succeed in this state but writes with write concern "majority" cannot succeed and the commit point starts to lag. If your PSA replica set contains a lagged secondary and your replica set requires two nodes to majority commit a change, your commit point also lags.

It's unclear to what situation "and the commit point starts to lag" refers to. Does it mean BOTH: "If one data-bearing node goes down", AND "writes with write concern "majority" cannot succeed"? Or does it ONLY refer to "writes with write concern "majority""?

In other words, does the lagging majority commit point in a degraded PSA can be mitigated by not using w:majority, or is it unavoidable as long as the secondary is down?

This is specific to MongoDB 5.0, where we cannot disable read majority anymore.