Skip to content

Commit 153e997

Browse files
author
Chris Cho
authored
DOCSP-35392: update laravel docs link (#940)
1 parent ca9b21d commit 153e997

File tree

2 files changed

+28
-21
lines changed

2 files changed

+28
-21
lines changed

REVIEWING.md

Lines changed: 22 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,42 +1,48 @@
1-
# Pull Request Reviewing Guidelines for Driver Ecosystem Documentation
1+
# Pull Request Reviewing Guidelines for the Driver Ecosystem Documentation
22

33
Contributions to the set of documents in this repository can receive reviews from one or both of the following types of reviews:
44

55
1. A **copy review**, which focuses on information structure and wording; typically performed by a MongoDB Documentation Team member
6-
2. A **technical review**, which addresses code snippets and the technical correctness of prose; typically performed by a MongoDB engineer.
6+
2. A **technical review**, which addresses code snippets and the technical correctness of prose, typically performed by a MongoDB engineer.
7+
8+
# Which Types of Changes for which to Request a Technical Review
9+
10+
- When the PR changes include code snippets.
11+
- When the PR changes include release notes, breaking changes, or upgrading versions.
12+
- To get alignment on specific wording of descriptions of technical information, especially for new features.
13+
- If in doubt, request a technical review.
14+
15+
# What to Review
716

817
See the following sections for reviewer expectations for each type of pull request (PR) review:
918

1019
## Copy Review
1120

12-
Review the structure, wording, and flow of the information in the PR, and correct it if necessary.
21+
A typical copy review consists of the following checks:
1322

14-
### What to Review
15-
16-
- Wording
23+
- Wording, including grammar and spelling
1724
- Page structure
18-
- Technical content to the extent of the reviewers understanding.
25+
- Technical content to the extent of the reviewer's understanding
1926
- Whether the PR fulfills the Acceptance Criteria described in the
20-
linked JIRA ticket.
27+
linked JIRA ticket
2128

2229
### What Not to Review
2330

24-
Nothing is completely off-limits to a copy review of a PR -- if you notice a technical issue, it's best to call it out early.
25-
Copy reviewers should constrain their reviews to content within the scope of the JIRA ticket, or otherwise create PRs to address anything unrelated.
26-
31+
Nothing is entirely off-limits to a copy review of a PR -- if you notice a technical issue, it's best to call it out early.
32+
Copy reviewers should constrain their reviews to content within the scope of the JIRA ticket or otherwise create PRs to address anything unrelated.
2733

2834
## Technical Review
2935

30-
Review the technical accuracy and completeness of a PR and correct it if necessary.
31-
32-
### What to Review
36+
A typical technical review consists of the following checks:
3337

34-
- Code snippets; ensure the code is idiomatic and that all technical claims are correct. e.g. ("To create a `Foo`, use the `Bar.createFoo()` method")
38+
- Technical accuracy
39+
- Release notes, breaking changes, and upgrading pages; ensure the technical claims are correct.
40+
- Code snippets: ensure the code is idiomatic and that all technical claims are correct. e.g. ("To create a `Foo`, use the `Bar.createFoo()` method")
3541
- Problematic explanations that could trip up users who try to follow the documentation.
3642

3743
### What Not to Review
3844

39-
While we welcome any recommendations on wording and structure, avoid blocking approval based on any copy edits. Please entrust the author to make the writing decisions based on style guidelines and team-specific writing conventions, and to create PRs to address anything they deem outside the technical review scope.
45+
While we welcome any recommendations on wording and structure, avoid blocking approval based on any copy edits. Please entrust the author to make the writing decisions based on style guidelines and team-specific writing conventions and to create PRs to address anything they deem outside the technical review scope.
4046

4147
- Wording of sentences, although corrections to technical claims are welcome
4248
- Structure of the page

source/php-libraries.txt

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -60,10 +60,11 @@ Framework Integrations
6060

6161
- Laravel
6262

63-
- `Laravel MongoDB <https://github.com/mongodb/laravel-mongodb>`__ is an
64-
Eloquent model and Query builder that supports MongoDB by using the
65-
original Laravel API. This library extends the original Laravel classes
66-
and therefore uses the same methods.
63+
- `Laravel MongoDB <https://www.mongodb.com/docs/drivers/php/laravel-mongodb/current/>`__
64+
is MongoDB's official Eloquent model and query builder that supports
65+
MongoDB by using the original Laravel API. This package extends the PHP
66+
Laravel classes to work with MongoDB as a datastore in your Laravel
67+
application.
6768

6869
- Symfony
6970

@@ -100,4 +101,4 @@ Tools and Projects
100101
a common way for programs to create, send, and read messages.
101102

102103
- `XHGui <https://github.com/perftools/xhgui>`__ is a web interface for the
103-
XHProf profiler, which stores profiling data in MongoDB.
104+
XHProf profiler, which stores profiling data in MongoDB.

0 commit comments

Comments
 (0)