From 5c8f8e06e6362c2e2ca0dae926ec316ec848c1a3 Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Fri, 29 Sep 2023 10:01:36 +0200 Subject: [PATCH] Fix typos (#672) Co-authored-by: hjpotter92 --- README.md | 2 +- docs/livepeer-in-a-box.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index c018367cb..a064235a4 100644 --- a/README.md +++ b/README.md @@ -174,7 +174,7 @@ where the `PLAYBACK_ID` is `foo`. ### Using OBS Studio -Under OBS Studio streaming settings, select "Serive" as "Custom..." +Under OBS Studio streaming settings, select "Service" as "Custom..." which should display text input options asking for "Server" and "Stream Key" (ref. screenshot below). Use following values for the same: diff --git a/docs/livepeer-in-a-box.md b/docs/livepeer-in-a-box.md index eae50da1d..6143fe509 100644 --- a/docs/livepeer-in-a-box.md +++ b/docs/livepeer-in-a-box.md @@ -172,7 +172,7 @@ example, if you're hacking on `task-runner`, you might have /home/user/code/task-runner ``` -The catalyst Makefile is aware of of the common paths for all of the other +The catalyst Makefile is aware of the common paths for all of the other projects that go into the full stack. All that's necessary to build a new binary, package it in the container, and trigger a restart is a single command: @@ -225,7 +225,7 @@ server. Additional note: in the interest of build speed, `make livepeer-api` does not package the frontend within the `livepeer-api` binary that it builds, so if you -experience your frontend suddently 404ing after you run `make livepeer-api` you +experience your frontend suddenly 404ing after you run `make livepeer-api` you will have to use the above instructions to boot up the frontend on your host. You can also build the full API server with a bundled frontend using