Skip to content

Commit 347168c

Browse files
committed
Unify vocabulary
1 parent d1ad0ae commit 347168c

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

content/terms/guidelines/declaring.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
2-
title: "Declaring documents"
2+
title: "Declaring terms"
33
---
44

5-
# Declaring documents
5+
# Declaring terms
66

77
## Service name
88

@@ -29,7 +29,7 @@ title: "Declaring documents"
2929

3030
### Provider prefixing
3131

32-
- If you encounter a document you want to add to a service, yet find that it would override an already-declared document for this service such as Terms of Service or Privacy Policy, and that the only solution you see would be to create a new terms type that would contain the name of the feature, then it is likely you should declare a new service, potentially duplicating existing documents.
32+
- If you encounter terms you want to add to a service, yet find that it would override already-declared terms for this service such as Terms of Service or Privacy Policy, and that the only solution you see would be to create a new terms type that would contain the name of the feature, then it is likely you should declare a new service, potentially duplicating existing terms.
3333

3434
> Example: the Facebook Community Payments terms are Terms of Service. The only way to declare them in the Facebook service would be to add a “Community Payments Terms” terms type as they would otherwise conflict with Facebook's Terms of Service. It is better to declare a new service called “Facebook Payments” with its own Terms of Service. It turns out that this service also has a developer agreement, independent from the main Facebook service.
3535
@@ -47,13 +47,13 @@ Noise is unwanted content in versions.
4747

4848
### Irrelevant content
4949

50-
The first type of noise we try to remove is content that is not **relevant legally speaking**, and that harms **document readability**.
50+
The first type of noise we try to remove is content that is not **relevant legally speaking**, and that harms **terms readability**.
5151

5252
**CSS selectors** are a first step as they permit to select an area instead of the whole page, but they let pass through content such as headers, footers, buttons, drop-down lists...
5353

5454
**Filtering** permits to get rid of the remaining irrelevant content.
5555

56-
A drop-down list let user select which document he would like to see but this list doesn't interest us in the final document.
56+
A drop-down list lets users select which terms they would like to see but this list doesn't interest us in the final version.
5757

5858
**HTML file :**
5959

0 commit comments

Comments
 (0)