diff --git a/pages/docs/data-structure/events-and-properties.md b/pages/docs/data-structure/events-and-properties.md
index a5bddbff5b..7198857660 100644
--- a/pages/docs/data-structure/events-and-properties.md
+++ b/pages/docs/data-structure/events-and-properties.md
@@ -35,7 +35,7 @@ We recommend striking the right balance when defining your events. Events should
 
 **For example:**
 
-* If your goal is to analyse at high-level how users traverse through different pages: instead of tracking multiple events `Home Page Viewed` and `Pricing Page Viewed`, track a `Page Viewed` event with a `Page Name` property set to **"/home"** or **"/pricing"**. See [Tracking Page Views](/docs/tracking-methods/sdks/javascript#tracking-page-views) in our Javascript SDK documentation on how to instrument this.
+* If your goal is to analyse at high-level how users traverse through different pages: instead of tracking multiple events `Home Page Viewed` and `Pricing Page Viewed`, track a `Page Viewed` event with a `Page Name` property set to **"\/home"** or **"\/pricing"**. See [Tracking Page Views](/docs/tracking-methods/sdks/javascript#tracking-page-views) in our Javascript SDK documentation on how to instrument this.
 
 * If your goal is to track users adding items to a shopping cart: instead of tracking multiple events `Add Shirt to Cart`, `Add Hoodie to Cart`, and `Add Socks to Cart`, track a `Add to Cart` event with a `Item` property set to **"Shirt"**, or **"Hoodie"**, or **"Socks"**.
 
diff --git a/pages/docs/tracking-methods/integrations/google-pubsub.md b/pages/docs/tracking-methods/integrations/google-pubsub.md
index a5b9aa0702..d2a38460a5 100644
--- a/pages/docs/tracking-methods/integrations/google-pubsub.md
+++ b/pages/docs/tracking-methods/integrations/google-pubsub.md
@@ -123,7 +123,7 @@ At this point, you can route events from your production Pub/Sub topic through a
 Once connected, this will result in a steady stream of events being sent to Mixpanel. Happy streaming!
 
 # Error Handling
-In rare instances, Mixpanel's /import API may return a 429 or 5XX error. These can be safely retried. We recommend an exponential backoff with jitter strategy, as written in the sample code above. PubSub can be configured to perform exponential backoff if the function itself times out.
+In rare instances, Mixpanel's \/import API may return a 429 or 5XX error. These can be safely retried. We recommend an exponential backoff with jitter strategy, as written in the sample code above. PubSub can be configured to perform exponential backoff if the function itself times out.
 
 If the payload is malformed, our API might return a 400 error. In this case, the item cannot be ingested and this error should not be retried. Enqueue these messages onto a dead-letter-queue for inspection later on. This might happen while initially testing the connector, but should be rare in production, assuming the shape of data flowing through the pipeline remains consistent.