diff --git a/changelog/0.10.0.md b/changelog/0.10.0.md
index 79be882e..f56d9da2 100644
--- a/changelog/0.10.0.md
+++ b/changelog/0.10.0.md
@@ -24,13 +24,13 @@
 - The `GraphQLObject`, `GraphQLInputObject`, and `GraphQLEnum` custom derives
   now parse doc strings and use them as descriptions. This behavior can be
   overridden by using an explicit GraphQL `description` annotation such as
-  `#[graphql(description = "my description")]`.
+  `#[graphql(description = "my description")]`. [View documentation](https://graphql-rust.github.io/types/objects/defining_objects.html#defining-objects).
 
   [#194](https://github.com/graphql-rust/juniper/issues/194)
 
 - Introduced `IntoFieldError` trait to allow custom error handling
   i.e. custom result type. The error type must implement this trait resolving
-  the errors into `FieldError`.
+  the errors into `FieldError`. [View documentation](https://graphql-rust.github.io/types/objects/error_handling.html#structured-errors).
 
   [#40](https://github.com/graphql-rust/juniper/issues/40)
 
@@ -40,7 +40,7 @@
 
 - Error responses no longer have a _data_ field, instead, error details are stored in the _extensions_ field
 
-  **Note:** while this is a breaking change, it is a necessary one to better align with the latest [GraphQL June 2018](https://facebook.github.io/graphql/June2018/#sec-Errors) specification, which defines the reserved _extensions_ field for error details.
+  **Note:** while this is a breaking change, it is a necessary one to better align with the latest [GraphQL June 2018](https://facebook.github.io/graphql/June2018/#sec-Errors) specification, which defines the reserved _extensions_ field for error details. [View documentation](https://graphql-rust.github.io/types/objects/error_handling.html#structured-errors).
 
   [#219](https://github.com/graphql-rust/juniper/pull/219)
 
@@ -49,7 +49,7 @@
 
   [#225](https://github.com/graphql-rust/juniper/issues/225)
 
-* When using the `GraphQLObject` custom derive, fields can now be omitted by annotating the field with `#[graphql(skip)]`.
+* When using the `GraphQLObject` custom derive, fields can now be omitted by annotating the field with `#[graphql(skip)]`. [View documentation](https://graphql-rust.github.io/types/objects/defining_objects.html#skipping-fields).
 
   [#220](https://github.com/graphql-rust/juniper/issues/220)