Misleading documentation: `mr_id` instead of `mr_iid`

## Description of the problem, including code/CLI snippet

https://github.com/python-gitlab/python-gitlab/blob/88693ff2d6f4eecf3c79d017df52738886e2d636/docs/gl_objects/merge_requests.rst?plain=1#L93-L119

"Most probably", here the author meant `mr_iid` and **not** `mr_id` (i.e. the project-agnostic ID).

If those are the only two instances, I'd open an MR to fix them now - but I'm thinking whether this a more widespread issue that I wouldn't know how to fix 😕 

## Expected Behavior


## Actual Behavior


## Specifications

  - python-gitlab version:
  - API version you are using (v3/v4):
  - Gitlab server version (or gitlab.com):


	Get a single MR::

	mr = project.mergerequests.get(mr_id)

	Create a MR::

	mr = project.mergerequests.create({'source_branch': 'cool_feature',
	'target_branch': 'main',
	'title': 'merge cool feature',
	'labels': ['label1', 'label2']})

	Update a MR::

	mr.description = 'New description'
	mr.labels = ['foo', 'bar']
	mr.save()

	Change the state of a MR (close or reopen)::

	mr.state_event = 'close' # or 'reopen'
	mr.save()

	Delete a MR::

	project.mergerequests.delete(mr_id)
	# or
	mr.delete()

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Misleading documentation: `mr_id` instead of `mr_iid` #2295

Description of the problem, including code/CLI snippet

Expected Behavior

Actual Behavior

Specifications

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Misleading documentation: mr_id instead of mr_iid #2295

Description

Description of the problem, including code/CLI snippet

Expected Behavior

Actual Behavior

Specifications

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Misleading documentation: `mr_id` instead of `mr_iid` #2295