modified refs to example repos

added examples as subfolders

public-site/docs/src/guides/authentication/index.md

@@ -113,7 +113,7 @@ It's possible to use a proxy in front of the client application that takes care
 
 ![Diagram](./radix-front-proxy.png "Application diagram")
 
-For an example using [oauth2_proxy](https://github.com/oauth2-proxy/oauth2-proxy/blob/master/docs/docs/configuration/overview.md) see [Radix oauth example](https://github.com/equinor/radix-example-oauth-proxy). [Radix Web Console](https://console.radix.equinor.com/) uses this service, and does API calls to radix-api through a [nginx reverse proxy](https://github.com/equinor/radix-web-console/blob/master/proxy/nginx.conf)
+For an example using [oauth2_proxy](https://github.com/oauth2-proxy/oauth2-proxy/blob/master/docs/docs/configuration/overview.md) see [Radix oauth example](../../../../../examples/radix-oauth-proxy/). [Radix Web Console](https://console.radix.equinor.com/) uses this service, and does API calls to radix-api through a [nginx reverse proxy](https://github.com/equinor/radix-web-console/blob/master/proxy/nginx.conf)
 
 Pro
 

public-site/docs/src/other/scenarios/index.md

@@ -15,5 +15,5 @@ App which authenticates the user in AD, if logged in read basic user information
 
 Example for Omnia Radix showing how to use a OAuth proxy for authentication
 
-- [Omnia Radix OAuth proxy for authentication](https://github.com/equinor/radix-example-oauth-proxy)
+- [Omnia Radix OAuth proxy for authentication](../../../../../examples/radix-oauth-proxy/)
 

public-site/docs/src/references/reference-radix-config/index.md

@@ -1030,7 +1030,7 @@ spec:
 
 It is possible to have multiple custom DNS aliases (i.e. to choose your own custom domains) for the application. The `dnsExternalAlias` needs to point to a component marked as public. It can be any domain name, which can in turn be used for public URLs to access the application — as long as the application developer provides a valid certificate for the alias.
 
-If public component is a `proxy` (like `oauth-proxy` in [this example](https://github.com/equinor/radix-example-oauth-proxy)), which is used as a public component, routing requests to `frontend` component - `dnsExternAlias.component` should point to this `proxy` component.
+If public component is a `proxy` (like `oauth-proxy`), which is used as a public component, routing requests to `frontend` component - `dnsExternAlias.component` should point to this `proxy` component.
 
 In the example above, the component **frontend** hosted in environment **prod** will be accessible from both `some.alias.com` and `another.alias.com`, as long as the correct certificate has been set.