fix: broken links

api-documentation/entry-point.md

@@ -129,4 +129,4 @@ Thus, an explicit statement should appear so the client can easily discover all
 
 ### Security considerations
 
-Please refer to the [security considerations](../1.1.security-considerations.md)  document.
+Please refer to the [security considerations](../security-considerations.md)  document.

api-documentation/generating-user-document.md

@@ -40,8 +40,8 @@ It is common to create project documentations, including end point details.
 By providing detailed description of the entry point API, it is possible to 
 create automated documentation generators.
 
-Communication would look like those described in [this](./1.entry-point.md), 
-[this](./2.api-documentation.md) and [this](./2.1.api-documentation-data-structures.md)
+Communication would look like those described in [this](./entry-point.md), 
+[this](./overview.md) and [this](./data-structures.md)
 documents.
 
 Resulting documentation should contain these details:

api-documentation/overview.md

@@ -141,6 +141,6 @@ Hydra Core Vocabulary specification would introduce several weaknesses in all ca
 - if the control extends API documentation behavior, there is no mechanism that would force it to override it instead
 
 ### More specific situations:
-- [API documentation data structures](./2.1.api-documentation-data-structures.md)
-- [API documentation user document](./2.2.api-documentation-user-document.md)
-- [Complete API documentation](./2.3.complete-api-documentation.md)
+- [API documentation data structures](./api-documentation-data-structures.md)
+- [API documentation user document](./generating-user-document.md)
+- [Complete API documentation](./complete-api-documentation.md)

drafts/6.updating-event.md

@@ -83,7 +83,7 @@ The event should be now updated.
 
 ### What does the term "update" means?
 
-As mentioned in the [previous use case](/4.obtaining-single-event.md), the application is not aware
+As mentioned in the [previous use case](./4.obtaining-single-event.md), the application is not aware
 of the kind of data that will be provided by the server, thus a simple question arises:
 
 *What gets updated?*

movies/0.index.md

@@ -7,7 +7,7 @@ The Hydra Movies API shows how a basic CRUD (Create, Read, Update, Delete) API c
 
 The following recipes decribe Hydra features that are used by the API.
 
-  * [1 API entry point](1.entry-point.md)
-  * [2 The JSON-LD context](movies/2.context.md)
-  * [3 The API documentation](movies/3.api-doc.md)
-  * [4 Create a movie](movies/4.create-movie.md)
+  * [1 API entry point](./1.entry-point.md)
+  * [2 The JSON-LD context](./2.context.md)
+  * [3 The API documentation](./3.api-doc.md)
+  * [4 Create a movie](./4.create-movie.md)