[Django] #34161: Wrong Name in Django Relationship

[Django]

#34161: Wrong Name in Django Relationship
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
Vshivam1710 |
Type: Bug | Status: new
Component: Database | Version: 4.1
layer (models, ORM) |
Severity: Normal | Keywords: ManyToManyField
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
I have read about the relationship on this page
[https://docs.djangoproject.com/en/4.1/topics/db/models/].

In this page Many-to-Many relationship information present. But by mistake
`ForeignKeyField` name placed reather then `ManyToManyField`.

Please check and correct it. Let me also share screenshot.

--
Ticket URL: <https://code.djangoproject.com/ticket/34161>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#34161: Wrong Name in Django Relationship
-------------------------------------+-------------------------------------

Reporter: Vshivam1710 | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: ManyToManyField | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Vshivam1710):

* Attachment "Screenshot from 2022-11-15 22-14-24.png" added.

Typo mistake

[Django]

#34161: Wrong Name in Django Relationship

---------------------------------+--------------------------------------
Reporter: Vshivam1710 | Owner: nobody
Type: Bug | Status: closed
Component: Documentation | Version: 4.1
Severity: Normal | Resolution: invalid

Keywords: ManyToManyField | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0

---------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):

* status: new => closed
* resolution: => invalid
* component: Database layer (models, ORM) => Documentation

Comment:

This page also contains information about `ForeignKey`. I don't see
anything wrong with this section.

--
Ticket URL: <https://code.djangoproject.com/ticket/34161#comment:1>