Skip to content

DOCSP-46866: Cleanup #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 37 commits into from
Jan 31, 2025
Merged

Conversation

norareidy
Copy link
Collaborator

@norareidy norareidy commented Jan 28, 2025

Copy link

netlify bot commented Jan 28, 2025

Deploy Preview for docs-django ready!

Name Link
🔨 Latest commit e7d69e6
🔍 Latest deploy log https://app.netlify.com/sites/docs-django/deploys/679cdff1c5d6970008f9a3a9
😎 Deploy Preview https://deploy-preview-14--docs-django.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@@ -17,7 +17,7 @@ to read data from the ``sample_mflix`` database.
.. procedure::
:style: connected

.. step:: Query the "users" collection for a specified email
.. step:: Query the users collection for a specified email
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why the removal of quotes? Should this be Users instead?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Usually we format collection names without quotes, monospaced (like here). But we also don't use monospace text in headers. However since this is a step, not a header, I'll change to users collection

@@ -42,7 +42,7 @@ to read data from the ``sample_mflix`` database.

<Viewer: Khal Drogo>

.. step:: Query the "movies" collection for specified runtime values
.. step:: Query the movies collection for specified runtime values
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as above

@@ -39,7 +39,7 @@ and delete functions on your model objects.
:language: python
:copyable:

.. step:: Insert a movie into the database
.. step:: Insert a Movie into the database
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this stay lowercase since it's not a proper noun?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Movie objects are capitalized; I'll add "object" after to make that clear

Copy link
Collaborator

@rachel-mack rachel-mack left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some small stuff:

@@ -15,7 +15,7 @@ Get Started with {+django-odm+}
:values: tutorial

.. meta::
:description: Learn how to create an app to connect to a MongoDB deployment by using Django MongoDB Backend.
:description: Learn how to create an app to connect to a MongoDB deployment by using {+framework+} MongoDB Backend.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we be using variables in the meta descriptions?

Copy link
Collaborator Author

@norareidy norareidy Jan 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought they didn't render correctly but just checked and they do! So I'll update the descriptions

Comment on lines 379 to 382
- ``options``: Specifies {+framework+} field options. This field is
optional. To view a list of available options, see `Field options
<{+django-docs+}/ref/models/fields/#field-options>`__
in the {+framework+} documentation.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would make this change in all the instances that use "This field is optional."

Suggested change
- ``options``: Specifies {+framework+} field options. This field is
optional. To view a list of available options, see `Field options
<{+django-docs+}/ref/models/fields/#field-options>`__
in the {+framework+} documentation.
- ``options`` (optional): Specifies {+framework+} field options. To view a list of available options, see `Field options
<{+django-docs+}/ref/models/fields/#field-options>`__
in the {+framework+} documentation.

Comment on lines 460 to 462
`Model field reference <{+django-docs+}/ref/models/fields/>`__
in the {+framework+} documentation.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To learn more about {+framework+} field types, see
`Model field reference <{+django-docs+}/ref/models/fields/>`__
in the {+framework+} documentation.
To learn more about {+framework+} field types, see the
`Model field reference <{+django-docs+}/ref/models/fields/>`__
in the {+framework+} documentation.

@norareidy norareidy merged commit ca7c6e7 into mongodb:master Jan 31, 2025
5 checks passed
@norareidy norareidy deleted the DOCSP-46866-cleanup branch January 31, 2025 14:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants