Skip to content

Commit d7286c4

Browse files
authored
Minor page spec updates
1 parent 0c75151 commit d7286c4

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

src/connections/spec/page.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: 'Spec: Page'
33
---
44

5-
The `page` call lets you record whenever a user sees a page of your website, along with any optional properties about the page. Calling `page` or [`screen`](/docs/connections/spec/screen/) in one of our [sources](/docs/connections/sources/) is one of the first steps to getting started with Segment.
5+
The `page` call lets you record whenever a user sees a page of your website, along with any optional properties about the page. Calling `page` or [`screen`](/docs/connections/spec/screen/) in a Segment [source](/docs/connections/sources/) is one of the first steps to getting started with Segment.
66

77
{% include components/reference-button.html href="https://university.segment.com/introduction-to-segment/299969?reg=1&referrer=docs" icon="media/academy.svg" title="Segment University: The Page Method" description="Check out our high-level overview of the Page method in Segment University. (Must be logged in to access.)" %}
88

@@ -21,7 +21,7 @@ Here's the payload of a typical `page` call with most [common fields](/docs/conn
2121
}
2222
```
2323

24-
And here's the corresponding Javascript event that would generate the above payload. If you're using Segment's Javascript library, the page name and URL are automatically gathered and passed as properties into the event payload:
24+
And here's the corresponding JavaScript event that would generate the above payload. If you're using Segment's JavaScript library, the page name and URL are automatically gathered and passed as properties into the event payload:
2525

2626
```js
2727
analytics.page("Retail Page","Home");
@@ -77,11 +77,11 @@ Here's a complete example of a `page` call:
7777

7878
Properties are extra pieces of information that describe the page. They can be anything you want.
7979

80-
We've reserved some properties that have semantic meanings, and we handle them in special ways. For example, we always expect `path` to be the URL path of a page, and `referrer` to be the URL of the previous page.
80+
Segment handles properties with semantic meanings in unique ways. For example, Segment always expect `path` to be a page's URL path, and `referrer` to be the previous page's URL.
8181

8282
You should **only use reserved properties for their intended meaning**.
8383

84-
Reserved properties we have standardized:
84+
Reserved properties Segment has standardized:
8585

8686
<table>
8787
<tr>
@@ -150,4 +150,4 @@ The keywords would most likely be the same as, or similar to, the keywords you w
150150
</tr>
151151
</table>
152152

153-
**Note:** In [analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/), we automatically send the following properties: `title`, `path`, `url`, `referrer`, and `search`.
153+
**Note:** In [analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/), Segment automatically send the following properties: `title`, `path`, `url`, `referrer`, and `search`.

0 commit comments

Comments
 (0)