Fixed some spelling issues and formatting problems (#107)

## 💸 TL;DR
<!-- What's the three sentence summary of purpose of the PR -->
Fixed some spelling issues and formatting problems.

---------

Co-authored-by: Xenc <mrjeeves@gmail.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Author: 3 people

docs/capabilities/analytics/journeys-receipts.md

@@ -47,7 +47,7 @@ Covered calls:
 
 ## Upgrade note for existing devs
 
-`startJourney()` changed from returning only the Journey ID information to returning the Journey ID plus a receipt. If you’re  upgrading existing code,  you  may need to update any custom response types, mocks, or destructuring assumptions so they account for the new `receipt` field.
+`startJourney()` changed from returning only the Journey ID information to returning the Journey ID plus a receipt. If you’re upgrading existing code, you may need to update any custom response types, mocks, or destructuring assumptions so they account for the new `receipt` field.
 
 For example, code that only typed the response as `{ journeyId: string }` should now expect:
 
@@ -72,8 +72,6 @@ For example, code that only typed the response as `{ journeyId: string }` should
 | `JOURNEY_RECEIPT_INVALID` | Event payload was invalid and was not recorded. | `Invalid: Event payload was not recorded.` |
 | `JOURNEY_RECEIPT_UNSPECIFIED` | Recording status could not be confirmed. | `Unknown: Telemetry recording status could not be confirmed.` |
 
-## 
-
 Example:
 
 ```javascript

docs/capabilities/notifications/pn-best-practices.md

@@ -7,7 +7,7 @@ Push notifications can help drive engagement, increase player retention, and bui
 This guide provides instructions for implementing developer-authored push notifications for Reddit games.
 
 :::note
-This is currently an experimental feature, and you'll need to[apply](../notifications/notifications-overview.md#how-to-apply) for a spot in our beta program to implement push notifications in your app.
+This is currently an experimental feature, and you'll need to [apply](../notifications/notifications-overview.md#how-to-apply) for a spot in our beta program to implement push notifications in your app.
 :::
 
 ## How it works

docs/guides/logged-out-users.mdx

@@ -96,8 +96,6 @@ export async function onLoginButtonClick(context: Context) {
 }
 ```
 
-####
-
 #### Trigger at natural breakpoints
 
 The login/sign-up flow reloads the page, so any in-memory game state will be lost unless you s[ave the logged-out game state](#save-the-logged-out-game-state).

docs/guides/migrate/devvit-singleton.md

@@ -34,7 +34,7 @@ Delete the `devvit.yaml` file from your project root. All configuration is now h
 
 ### 3. Handle static assets
 
-If your app uses static assets (images, fonts, etc.) from an `assets` folder, you'll need to define this in update your `devvit.json` to point to these assets:
+If your app uses static assets (images, fonts, etc.) from an `assets` folder, you'll need to update your `devvit.json` to point to these assets:
 
 ```json
 {

docs/guides/migrate/inline-web-view.md

@@ -16,7 +16,7 @@ Apps can be partially migrated, you don't need to re-write everything!
 
 - No postMessage required
 - Use web native fetch() to server endpoints directly
-- App logic is either on the client, or the server, with clear deliniation
+- App logic is either on the client, or the server, with clear delineation
 - Client effects are available directly from web views
 
 ## Setting up devvit.json
@@ -161,8 +161,6 @@ server.listen(port, () => console.log(`http://localhost:${port}`));
 
 ### Calling your server endpoints
 
-Now
-
 Instead of using `postMessage`, your client-side code can now directly fetch the initial state from the `/api/init` endpoint we defined in the server.
 
 ```ts title=/src/client/app.ts

docs/guides/migrate/public-api.md

@@ -1,7 +1,7 @@
 # Migrating from PRAW to Devvit Web
 
 [Devvit Web](../../capabilities/devvit-web/devvit_web_overview.mdx) is how
-you ship the same kind of automation **on Reddit’s platform**. This guide will outline the basics
+you ship the same kind of automation **on Reddit’s platform**. This guide will outline the basics of migrating from PRAW to Devvit Web.
 
 :::note
 This guide assumes you have basic familiarity with Python and PRAW (e.g., `pip`, `requirements.txt`, and

versioned_docs/version-0.12/guides/migrate/devvit-singleton.md

@@ -34,7 +34,7 @@ Delete the `devvit.yaml` file from your project root. All configuration is now h
 
 ### 3. Handle static assets
 
-If your app uses static assets (images, fonts, etc.) from an `assets` folder, you'll need to define this in update your `devvit.json` to point to these assets:
+If your app uses static assets (images, fonts, etc.) from an `assets` folder, you'll need to update your `devvit.json` to point to these assets:
 
 ```json
 {

versioned_docs/version-0.12/guides/migrate/inline-web-view.md

@@ -16,7 +16,7 @@ Apps can be partially migrated, you don't need to re-write everything!
 
 - No postMessage required
 - Use web native fetch() to server endpoints directly
-- App logic is either on the client, or the server, with clear deliniation
+- App logic is either on the client, or the server, with clear delineation
 - Client effects are available directly from web views
 
 ## Setting up devvit.json
@@ -161,8 +161,6 @@ server.listen(port, () => console.log(`http://localhost:${port}`));
 
 ### Calling your server endpoints
 
-Now
-
 Instead of using `postMessage`, your client-side code can now directly fetch the initial state from the `/api/init` endpoint we defined in the server.
 
 ```ts title=/src/client/app.ts