docs: Fix links

Author: rjmunro

packages/documentation/docs/user-guide/concepts-and-architecture.md

@@ -27,7 +27,7 @@ To be able to facilitate various different kinds of show, Sofie Core has th
 - The **System** defines the whole of the Sofie Core
 - The **Organization** \(only available if user accounts are enabled\) defines things that are common for an organization. An organization consists of: **Users, Studios** and **ShowStyles**.
 - The **Studio** contains things that are related to the "hardware" or "rig". Technically, a Studio is defined as an entity that can have one \(or none\) rundown active at any given time. In most cases, this will be a representation of your gallery, with cameras, video playback and graphics systems, external inputs, sound mixers, lighting controls and so on. A single System can easily control multiple Studios.
-- The **Show Style** contains settings for the "show", for example if there's a "Morning Show" and an "Afternoon Show" - produced in the same gallery - they might be two different Show Styles \(played in the same Studio\). Most importantly, the Show Style decides the "look and feel" of the Show towards the producer/director, dictating how data ingested from the NRCS will be interpreted and how the user will interact with the system during playback (see: [Show Style](../configuration/settings-view#show-style) in Settings).
+- The **Show Style** contains settings for the "show", for example if there's a "Morning Show" and an "Afternoon Show" - produced in the same gallery - they might be two different Show Styles \(played in the same Studio\). Most importantly, the Show Style decides the "look and feel" of the Show towards the producer/director, dictating how data ingested from the NRCS will be interpreted and how the user will interact with the system during playback (see: [Show Style](configuration/settings-view#show-style) in Settings).
   - A **Show Style Variant** is a set of Show Style _Blueprint_ configuration values, that allows to use the same interaction model across multiple Shows with potentially different assets, changing the outward look of the Show: for example news programs with different hosts produced from the same Studio, but with different light setups, backscreen and overlay graphics.
 
 ![Sofie Architecture Venn Diagram](/img/docs/main/features/sofie-venn-diagram.png)
@@ -111,19 +111,19 @@ There are 3 types of blueprints, and all 3 must be uploaded into Sofie before th
 
 Handle things on the _System level_.  
 Documentation on the interface to be exposed by the Blueprint:  
-[https://github.com/nrkno/sofie-core/blob/master/packages/blueprints-integration/src/api.ts#L75](https://github.com/nrkno/sofie-core/blob/master/packages/blueprints-integration/src/api.ts#L75)
+[https://github.com/nrkno/sofie-core/blob/master/packages/blueprints-integration/src/api/system.ts](https://github.com/nrkno/sofie-core/blob/master/packages/blueprints-integration/src/api/system.ts)
 
 ### Studio Blueprints
 
 Handle things on the _Studio level_, like "which showstyle to use for this rundown".  
 Documentation on the interface to be exposed by the Blueprint:  
-[https://github.com/nrkno/sofie-core/blob/master/packages/blueprints-integration/src/api.ts#L85](https://github.com/nrkno/sofie-core/blob/master/packages/blueprints-integration/src/api.ts#L85)
+[https://github.com/nrkno/sofie-core/blob/master/packages/blueprints-integration/src/api/studio.ts](https://github.com/nrkno/sofie-core/blob/master/packages/blueprints-integration/src/api/studio.ts)
 
 ### Showstyle Blueprints
 
 Handle things on the _Showstyle level_, like generating [_Baseline_](#baseline), _Segments_, _Parts, Pieces_ and _Timelines_ in a rundown.  
 Documentation on the interface to be exposed by the Blueprint:  
-[https://github.com/nrkno/sofie-core/blob/master/packages/blueprints-integration/src/api.ts#L117](https://github.com/nrkno/sofie-core/blob/master/packages/blueprints-integration/src/api.ts#L117)
+[https://github.com/nrkno/sofie-core/blob/master/packages/blueprints-integration/src/api/showStyle.ts](https://github.com/nrkno/sofie-core/blob/master/packages/blueprints-integration/src/api/showStyle.ts)
 
 ## `PartInstances` and `PieceInstances`
 

packages/documentation/docs/user-guide/features/api.md

@@ -16,4 +16,4 @@ Starting with version 1.50.0, there is also a separate service available, called
 
 ## DDP – Core Integration
 
-If you're planning to build NodeJS applications that talk to _Sofie Core_, we recommend using the [core-integration](https://github.com/nrkno/sofie-core/tree/master/packages/server-core-integration.md) library, which exposes a number of callable methods and allows for subscribing to data the same way the [Gateways](../concepts-and-architecture.md#gateways) do it.
+If you're planning to build NodeJS applications that talk to _Sofie Core_, we recommend using the [core-integration](https://github.com/nrkno/sofie-core/tree/master/packages/server-core-integration) library, which exposes a number of callable methods and allows for subscribing to data the same way the [Gateways](../concepts-and-architecture.md#gateways) do it.

packages/documentation/docs/user-guide/further-reading.md

@@ -19,15 +19,15 @@ description: This guide has a lot of links. Here they are all listed by section.
 - [Windows install for Docker](https://hub.docker.com/editions/community/docker-ce-desktop-windows)
 - [Linux install instructions for Docker](https://docs.docker.com/install/linux/docker-ce/ubuntu/)
 - [Linux install instructions for Docker Compose](https://www.digitalocean.com/community/tutorials/how-to-install-docker-compose-on-ubuntu-18-04)
-- [Sofie Core Docker File Download](https://firebasestorage.googleapis.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LWRCgfY_-kYo9iX6UNy%2F-Lo5eWjgoVlRRDeFzLuO%2F-Lo5fLSSyM1eO6OXScew%2Fdocker-compose.yaml?alt=media&token=fc2fbe79-365c-4817-b270-e507c6a6e3c6)
+- [Sofie Core Docker File Download](https://hub.docker.com/r/sofietv/tv-automation-server-core)
 
 ### Installing a Gateway
 
 #### Ingest Gateways and NRCS
 
 - [MOS Protocol Overview & Documentation](http://mosprotocol.com/)
-- Information about ENPS on [The Associated Press' Website](https://www.ap.org/enps/support)
-- Information about iNews: [Avid's Website](https://www.avid.com/products/inews/how-to-buy)
+- Information about ENPS on [The Associated Press' Website](https://workflow.ap.org/)
+- Information about iNews: [Avid's Website](https://www.avid.com/solutions/news-production)
 
 **Google Spreadsheet Gateway**
 

packages/documentation/docs/user-guide/installation/installing-a-gateway/rundown-or-newsroom-system-connection/inews-gateway.md

@@ -8,4 +8,4 @@ The iNEWS Gateway allows you to create rundowns from within iNEWS and sync them
 
 The setup for the iNEWS Gateway is already in the Docker Compose file you downloaded earlier. Remove the _\#_ symbol from the start of the line labeled `image: tv2/inews-ftp-gateway:develop` and add a _\#_ to the other ingest gateway that was being used.
 
-Although the iNEWS Gateway is available free of charge, an iNEWS license is not. Visit [Avid's website](https://www.avid.com/products/inews/how-to-buy) to find an iNEWS reseller that handles your geographic area.
+Although the iNEWS Gateway is available free of charge, an iNEWS license is not. Visit [Avid's website](https://www.avid.com/solutions/news-production) to find an iNEWS reseller that handles your geographic area.

packages/documentation/docs/user-guide/installation/installing-a-gateway/rundown-or-newsroom-system-connection/intro.md

@@ -7,5 +7,5 @@ The Google Spreadsheet Gateway, iNEWS Gateway, and the MOS \( [Media Object Serv
 ### Further Reading
 
 - [MOS Protocol Overview & Documentation](http://mosprotocol.com/)
-- [iNEWS on Avid's Website](https://www.avid.com/products/inews/how-to-buy)
+- [iNEWS on Avid's Website](https://www.avid.com/solutions/news-production)
 - [ENPS on The Associated Press' Website](https://workflow.ap.org/)