Skip to content

Commit 71ba1f7

Browse files
authored
docs: fix small spelling issues (#680)
This commit fixes some small spelling issues.
1 parent 902fa49 commit 71ba1f7

File tree

6 files changed

+8
-8
lines changed

6 files changed

+8
-8
lines changed

developers/core-concepts/core-api/asset.mdx

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ webhook will be fired.
1818
#### Playback
1919

2020
An asset can be easily viewed by passing a `playbackId` to Livepeer's
21-
[Player](/developers/core-concepts/player). If using a third party player, then
21+
[Player](/developers/core-concepts/player). If using a third-party player, then
2222
the full playback url is required. This can be fetched from the
2323
[Playback Info](/api-reference/playback/get) API endpoint.
2424

developers/core-concepts/core-api/multistream.mdx

+2-2
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Facebook Live, and YouTube Live. This feature ensures that users can maximize
44
their audience reach across multiple platforms with a single streaming session.
55

66
When setting up a multistream, users have the option to utilize the Livepeer
7-
Studio Dashboard, directly interface with Livepeer Studio API, or the Livepeer
7+
Studio Dashboard, directly interfaces with Livepeer Studio API, or the Livepeer
88
Studio SDKs. These offer comprehensive management tools to configure, modify, or
99
delete specific multistream targets linked with individual streams. It's
1010
important to note that configurations are stream-specific; hence, they don't
@@ -30,7 +30,7 @@ of the ingest rate for the active source stream.
3030

3131
#### Webhooks
3232

33-
Additionally, Livepeer have three webhooks to monitor multistream targets:
33+
Additionally, Livepeer has three webhooks to monitor multistream targets:
3434

3535
1. `multistream.connected`: Indicates a successful connection to the multistream
3636
target and confirms the stream's live status on the corresponding service.

developers/core-concepts/core-api/stream.mdx

+2-2
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ given stream.
2525

2626
#### Recording
2727

28-
If recording is enabled, there are a set of webhook events which can notify your
28+
If recording is enabled, there is a set of webhook events which can notify your
2929
backend of a recording’s state transitions, including: `recording.ready`,
3030
`recording.started`, and `recording.waiting`. The recording is stored as an
3131
[asset](/developers/core-concepts/core-api/asset#recording).
@@ -52,7 +52,7 @@ Also, Livepeer provides
5252
allow a more comprehensive look into viewer behavior using the
5353
[livepeer viewership API](/api-reference/viewership/get-viewership-metrics).
5454
Reporting is enabled by default in the Livepeer Player, and can be integrated
55-
into any third party player.
55+
into any third-party player.
5656

5757
#### Playback
5858

developers/core-concepts/livepeer-network/orchestrators.mdx

+1-1
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ For ease of operation and to ensure they are accessible for jobs, Orchestrators
3838
are required to set up specific parameters and ensure they have the necessary
3939
prerequisites, including proper networking configurations, accessibility to
4040
Arbitrum nodes, sufficient bandwidth, and more. They can also manage their ETH
41-
accounts for transactions and rewards either manually or let the Livepeer system
41+
accounts for transactions and rewards either manually or by letting the Livepeer system
4242
handle it automatically.
4343

4444
Orchestrators are essential components of the Livepeer ecosystem, offering their

developers/guides/clip-a-livestream.mdx

+1-1
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Submit a request to the [Create Clip API](/api-reference/stream/create-clip)
3636
using the following request parameters:
3737

3838
<ParamField path="startTime" type="number">
39-
UNIX timestamp (in milliseconds) of clip's start from the browser’s playhead
39+
UNIX timestamp (in milliseconds) of clip's starts from the browser’s playhead
4040
(commonly supplied by HLS players).
4141
</ParamField>
4242

developers/guides/get-engagement-analytics-via-api.mdx

+1-1
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ rebuffer ratio, and exit-before-starts across a variety of dimensions.
1515
`@livepeer/react` version 4.2.0 or higher.
1616
</Info>
1717

18-
This API includes realtime metrics about the ongoing livestream or VOD engagement:
18+
This API includes real-time metrics about the ongoing livestream or VOD engagement:
1919

2020
- Viewer Count: The number of viewers currently watching the stream (or VOD).
2121
- Error Rate: This metric helps to understand the number of errors that viewers are

0 commit comments

Comments
 (0)