Skip to content

Fixed typos #630

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.

Sign up for GitHub

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 1 commit into from
Oct 24, 2018
Merged

Fixed typos #630

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 core/angularjs-integration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,4 +97,4 @@ admin.addEntity(article);
nga.configure(admin);
```

You can look at what we have done as another exemple [api-platform/admin](https://github.com/api-platform/admin).
You can look at what we have done as another example [api-platform/admin](https://github.com/api-platform/admin).
2 changes: 1 addition & 1 deletion core/filters.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -896,7 +896,7 @@ final class UserFilter extends SQLFilter
public function addFilterConstraint(ClassMetadata $targetEntity, string $targetTableAlias): string
{
if (null === $this->reader) {
return throw new \RuntimeException(sprintf('An annotation reader must be provided. Be sure to call "%s::setAnnotationReader()".', __CLASS__));
throw new \RuntimeException(sprintf('An annotation reader must be provided. Be sure to call "%s::setAnnotationReader()".', __CLASS__));
}

// The Doctrine filter is called for any query on any entity
Expand Down
2 changes: 1 addition & 1 deletion core/serialization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -210,7 +210,7 @@ In the following JSON document, the relation from a book to an author is represe
```

However, for performance reasons, it is sometimes preferable to avoid forcing the client to issue extra HTTP requests.
It is possible to embed related objects (in their entirity, or only some of their properties) directly in the parent
It is possible to embed related objects (in their entirety, or only some of their properties) directly in the parent
response through the use of serialization groups. By using the following serialization groups annotations (`@Groups`),
a JSON representation of the author is embedded in the book response:

Expand Down
4 changes: 2 additions & 2 deletions schema-generator/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ Example:
types:
Brand:
properties:
logo: { range: "ImageObject" } # Force the range of the logo propery to ImageObject (can also be URL according to Schema.org)
logo: { range: "ImageObject" } # Force the range of the logo property to ImageObject (can also be URL according to Schema.org)

PostalAddress:
properties:
Expand Down Expand Up @@ -372,7 +372,7 @@ doctrine:
## Changing the Field Visibility

Generated fields have a `private` visibility and are exposed through getters and setters.
The default visibility can be changed with the `fieldVisibility` otion.
The default visibility can be changed with the `fieldVisibility` option.

Example:

Expand Down