diff --git a/docs/how/metadata-modelling.md b/docs/how/metadata-modelling.md
index 8fa47aa620..fdd5a89f0c 100644
--- a/docs/how/metadata-modelling.md
+++ b/docs/how/metadata-modelling.md
@@ -1,5 +1,5 @@
 # How to model metadata ?
-[GMA](../what/gma.md) uses [rest.li](https://rest.li), which is LinkedIn's open source REST framework. All metadata in GMA needs to be modelled using [Pegasus schema (PDSC)](https://linkedin.github.io/rest.li/DATA-Data-Schema-and-Templates) which is the data schema for [rest.li](https://rest.li).
+[GMA](../what/gma.md) uses [rest.li](https://rest.li), which is LinkedIn's open source REST framework. All metadata in GMA needs to be modelled using [Pegasus schema (PDSC)](https://linkedin.github.io/rest.li/pdsc_syntax) which is the data schema for [rest.li](https://rest.li).
 
 Conceptually we’re modelling metadata as a hybrid graph of nodes ([entities](../what/entity.md)) and edges ([relationships](../what/relationship.md)), with additional documents ([metadata aspects](../what/aspect.md)) attached to each node. You can also think of it as a modified [Entity-Relationship Model](https://en.wikipedia.org/wiki/Entity%E2%80%93relationship_model).