Merge branch 'master' into remove_dest_filter_device_beta

Author: markzegarelli

src/connections/destinations/catalog/castle/index.md

@@ -2,7 +2,7 @@
 title: Castle Destination
 ---
 
-Once you enable the Castle integration, the [Castle JavaScript snippet](https://castle.io/docs/tracking) is placed on your website, and user data starts appearing in the Castle dashboard.
+Once you enable the Castle integration, the [Castle JavaScript snippet](https://docs.castle.io/v1/tutorials/client-side-integration/web/) is placed on your website, and user data starts appearing in the Castle dashboard.
 Client-side tracking works out of the box, however **your existing server-side calls need to be extended** with data from the incoming request.
 
 Castle supports calling `identify`, `page`, `screen`, and `group`. Castle does *not* support the `alias` call.

src/connections/sources/catalog/libraries/server/net/quickstart.md

@@ -16,7 +16,7 @@ The best analytics installation combines both client-side and server-side tracki
 
 Before you begin, you need a Workspace (which is a container that holds all of the sources and destinations which are billed together for an organization). If you already created one, great! If not, you can sign up for a free Segment account and create one.
 
-Next, create a Ruby source from your Workspace:
+Next, create a .NET source from your Workspace:
 
 1. Click **Add Source**.
 2. From the source catalog page, click **.NET**.