Skip to content

Small changes for formatting and grammar #546

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 3 commits into from
Jul 29, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _includes/common/performance.md
Original file line number Diff line number Diff line change
Expand Up @@ -1290,7 +1290,7 @@ There are some limits in place to ensure the API can provide the data you need i

* Queries return 100 objects by default. Use the `limit` parameter to change this.
* Skips and limits can only be used on the outer query.
* Constraints that collide with each other will result in only one of the constraint being applied. An example of this would be two `equalTo` constraints over the same key with two different values, which contradicts itself (perhaps you're looking for 'contains').
* Constraints that collide with each other will result in only one of the constraints being applied. An example of this would be two `equalTo` constraints over the same key with two different values, which contradicts itself (perhaps you're looking for 'contains').
* No geo-queries inside compound OR queries.
* Using `$exists: false` is not advised.
* The `each` query method in the JavaScript SDK cannot be used in conjunction with queries using geo-point constraints.
Expand Down
2 changes: 1 addition & 1 deletion _includes/parse-server/cache-adapters.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ var api = new ParseServer({
});
```

The `redisOptions` are passed directly to the redis.createClient method. For more informations, refer to the [redis.createClient](https://www.npmjs.com/package/redis#rediscreateclient) documentation.
The `redisOptions` are passed directly to the redis.createClient method. For more information refer to the [redis.createClient](https://www.npmjs.com/package/redis#rediscreateclient) documentation.

Note that at the moment, only passing a single argument is supported.

Expand Down
2 changes: 1 addition & 1 deletion _includes/parse-server/deploying-heroku-mlab.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Here are the steps:
2. Create a Heroku account (if you don’t have one already) and use the Heroku Toolbelt to log in and prepare a new app in the same directory as your Express app. Take a look at Heroku's [Getting Started with Node.js guide](https://devcenter.heroku.com/articles/getting-started-with-nodejs#introduction) for more details.
3. Use the mLab addon: `heroku addons:create mongolab:sandbox` (or, you can create a Mongo instance yourself, either directly with mLab or your own box)
4. Use heroku config and note the URI provided by mLab under the var MONGOLAB_URI
5. Copy this URI and set it as a new config variable: heroku config:set `DATABASE_URI=mongodb://...`
5. Copy this URI and set it as a new config variable: `heroku config:set DATABASE_URI=mongodb://...`
6. Deploy it: `git push heroku master`

You may also refer to the Heroku Dev Center article on [Deploying a Parse Server to Heroku](https://devcenter.heroku.com/articles/deploying-a-parse-server-to-heroku).