Is NvEncUnmapInputResource really required after NvEncLockBitstream?

I have a situation where I’d like to leave my buffer mapped, because I want to send it back through the encoder for another frame (repeated frames). The header file states

The client must unmap the buffer after ::NvEncLockBitstream() API returns successfully for encode work submitted using the mapped input buffer.

Is this just a case of verbage being unclear, and I don’t really have to unmap it. It is just trying to tell me if I want to unmap it, I need to wait for the lock to succeed, but I don’t have to unmap it?

Can I safely leave the buffer mapped?