You can't repush the same version number with changes. The RubyGems FAQ explains:
Why can't I repush a gem version? This causes several problems to start happening:
- Mirrors that comb the site (with gem mirror) would be out of sync.
- Clients can't verify the contents of gems (via MD5 or something similar) so they could download different versions, expecting the same code.
- You're not going to run out of gem versions, just push a new one.
It's that last part that's most relevant here. You're not going to run out of gem versions, so update the documentation and bump the patch version or roll the documentation updates in with the next set of patch level changes.