Skip to content

fixing a typo #255

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

Closed
wants to merge 2 commits into from
Closed

fixing a typo #255

wants to merge 2 commits into from

Conversation

bgrabar
Copy link

@bgrabar bgrabar commented Sep 21, 2012

No description provided.

@bgrabar
Copy link
Author

bgrabar commented Sep 21, 2012

I'd committed "DOCS-508 early edits" on a different branch. The edits should not have shown up on the "fixing a typo" branch. Clearly there is something I missed.

@epc
Copy link
Contributor

epc commented Sep 21, 2012

I won't do anything until Sam can review.
I had a glitch earlier this week where I pushed some changes that I didn't expect to show up at all, wonder the routine I'm using is wrong.

``0``, which means they can never seek :ref:`election
<replica-set-elections>` as primary. For more information on priority
levels, see :ref:`replica-set-node-priority`.

Copy link
Contributor

Choose a reason for hiding this comment

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

This document should be in draft, as it doesn't look complete.

@bgrabar bgrabar closed this Sep 25, 2012
mongo-cr-bot pushed a commit that referenced this pull request Jan 10, 2022
mongodb-server-docs-sync-bot bot pushed a commit that referenced this pull request Jun 6, 2025
* DOCSP-50268-Release-notes-Relational-Migrator-1.13.2-fast-follow

* Mismatched backticks.
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