Skip to content
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

[AutoPR servicefabric/data-plane] Fix unrecognized character in service fabric data plane swagger file #3164

Merged
merged 1 commit into from
Aug 28, 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
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ class ServicePlacementPreferPrimaryDomainPolicyDescription(ServicePlacementPolic
particular domain.
This placement policy is usually used with fault domains in scenarios where
the Service Fabric cluster is geographically distributed in order to
indicate that a services primary replica should be located in a particular
indicate that a service's primary replica should be located in a particular
fault domain, which in geo-distributed scenarios usually aligns with
regional or datacenter boundaries. Note that since this is an optimization
it is possible that the Primary replica may not end up located in this
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ class ServicePlacementPreferPrimaryDomainPolicyDescription(ServicePlacementPolic
particular domain.
This placement policy is usually used with fault domains in scenarios where
the Service Fabric cluster is geographically distributed in order to
indicate that a services primary replica should be located in a particular
indicate that a service's primary replica should be located in a particular
fault domain, which in geo-distributed scenarios usually aligns with
regional or datacenter boundaries. Note that since this is an optimization
it is possible that the Primary replica may not end up located in this
Expand Down