DOCSP-45175: Connect to MongoDB

[norareidy]

Pull Request Info

PR Reviewing Guidelines

JIRA - https://jira.mongodb.org/browse/DOCSP-45175

Staging Links

get-started/connect-to-mongodb

get-started/next-steps

get-started

get-started/download-and-install

Self-Review Checklist

• Is this free of any warnings or errors in the RST?
• Did you run a spell-check?
• Did you run a grammar-check?
• Are all the links working?
• Are the facets and meta keywords accurate?

[netlify]

✅ Deploy Preview for docs-ruby ready!

Name	Link
🔨 Latest commit	7d22708
🔍 Latest deploy log	https://app.netlify.com/sites/docs-ruby/deploys/6759ac1aa5468f00088435d9
😎 Deploy Preview	https://deploy-preview-95--docs-ruby.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[jordan-smith721]

A couple suggestions but otherwise LGTM!

[jordan-smith721]

S: Split this last sentence since it's a bit long and hard to follow

Suggested change

	directory. Copy and paste the following code under the Bundler
	code from the :ref:`ruby-quick-start-download-and-install` step
	of this tutorial to query the ``movies`` collection in the ``sample_mflix``
	database:
	directory. Copy and paste the following code below the Bundler
	code from the :ref:`ruby-quick-start-download-and-install` step
	of this tutorial. This code connects to MongoDB and queries the
	``movies`` collection in the ``sample_mflix`` database.

[jordan-smith721]

S: Be specific about where to run this from since the first step had them navigate away from the directory

Suggested change

	In your project directory, run the following shell command to run the application:
	Navigate back to your ``ruby-quickstart`` directory and run the following shell command to run the application:

[comandeo-mongo]

Suggested change

	client.close
	rescue => e
	raise "Unable to find the document due to the following error: #{e}"
	end
	ensure
	client&.close
	end

I do not think we need to catch errors here only to print them - uncatched errors will be printed to stderr anyways. Instead, we may put closing the client into ensure, this is a good practice. We also use & in the client&.close because client can be nil theoretically (if client creation failed).