Fix dead links #883

docs/src/atomic-data-overview.md

@@ -21,7 +21,7 @@ Atomic Data has been designed with [the following goals in mind](motivation.md):
 - Make it easier for developers to build highly interoperable apps
 - Make standardization easier and cheaper
 
-Atomic Data is [Linked Data](https://ontola.io/what-is-linked-data/), as it is a [strict subset of RDF](interoperability/rdf.md).
+Atomic Data is [Linked Data](https://ontola.io/blog/what-is-linked-data/), as it is a [strict subset of RDF](interoperability/rdf.md).
 It is type-safe (you know if something is a `string`, `number`, `date`, `URL`, etc.) and extensible through [Atomic Schema](schema/intro.md), which means that you can re-use or define your own Classes, Properties and Datatypes.
 
 The default serialization format for Atomic Data is [JSON-AD](core/json-ad.md), which is simply JSON where each key is a URL of an Atomic Property.

docs/src/motivation.md

@@ -44,7 +44,7 @@ If Atomic Data will be successful, there will likely be other, better implementa
 
 ## Linked data is awesome, but it is too difficult for developers in its current form
 
-[Linked data](https://ontola.io/what-is-linked-data/) (RDF / the semantic web) enables us to use the web as a large, decentralized graph database.
+[Linked data](https://ontola.io/blog/what-is-linked-data/) (RDF / the semantic web) enables us to use the web as a large, decentralized graph database.
 Using links everywhere in data has amazing merits: links remove ambiguity, they enable exploration, they enable connected datasets.
 But the existing specs are too difficult to use, and that is harming adoption.