fix(fosrest): wrong internal links (#1494)

Author: COil

core/migrate-from-fosrestbundle.md

@@ -21,7 +21,7 @@ See [The view layer](https://github.com/FriendsOfSymfony/FOSRestBundle/blob/3.x/
 
 Add the `ApiResource` attribute to your entities, and enable operations you desire inside. By default, every operations are activated.
 
-See [Operations](../operations.md).
+See [Operations](operations.md).
 
 ### Make custom controllers
 
@@ -31,11 +31,11 @@ Same as above.
 
 **In API Platform**
 
-Even though this is not recommended, API Platform allows you to [create custom controllers](../controllers.md) and declare them in your entity's `ApiResource` attribute.
+Even though this is not recommended, API Platform allows you to [create custom controllers](controllers.md) and declare them in your entity's `ApiResource` attribute.
 
-You can use them as you migrate from FOSRestBundle, but you should consider [switching to Symfony Messenger](../messenger.md) as it will give you more benefits, such as compatibility with both REST and GraphQL, and better performances of your API on big tasks.
+You can use them as you migrate from FOSRestBundle, but you should consider [switching to Symfony Messenger](messenger.md) as it will give you more benefits, such as compatibility with both REST and GraphQL, and better performances of your API on big tasks.
 
-See [General Design Considerations](../design.md).
+See [General Design Considerations](design.md).
 
 
 ### Routing system (with native documentation support)
@@ -50,7 +50,7 @@ See [Full default annotations](https://github.com/FriendsOfSymfony/FOSRestBundle
 
 Use the `ApiResource` attribute to activate the HTTP methods you need for your entity. By default, all the methods are enabled.
 
-See [Operations](../operations.md).
+See [Operations](operations.md).
 
 ### Hook into the requests handling
 
@@ -64,7 +64,7 @@ See [Listener support](https://github.com/FriendsOfSymfony/FOSRestBundle/blob/3.
 
 API Platform provides a lot of ways to customize the behavior of your API, depending on what you exactly want to do.
 
-See [Extending API Platform](../extending.md) for more details.
+See [Extending API Platform](extending.md) for more details.
 
 ### Customize the formats of the requests and the responses
 
@@ -82,7 +82,7 @@ Both the request and the response body's format can be customized.
 
 You can configure the formats of the API either globally or in specific resources or operations. API Platform provides native support for multiple formats including JSON, XML, CSV, YAML, etc.
 
-See [Content negociation](../content-negotiation.md).
+See [Content negociation](content-negotiation.md).
 
 ### Name conversion
 
@@ -100,7 +100,7 @@ Both request and response bodies can be converted.
 
 API Platform uses [name converters](https://symfony.com/doc/current/components/serializer.html#component-serializer-converting-property-names-when-serializing-and-deserializing) included in the Serializer component of Symfony. You can create your own by implementing the `NameConverterInterface` provided by Symfony.
 
-See [_Name Conversion_ in The Serialization Process](../serialization.md#name-conversion).
+See [_Name Conversion_ in The Serialization Process](serialization.md#name-conversion).
 
 ### Handle errors
 
@@ -114,7 +114,7 @@ See [ExceptionController support](https://github.com/FriendsOfSymfony/FOSRestBun
 
 Map the exceptions to HTTP statuses in the `api_platform.exception_to_status` parameter.
 
-See [Errors Handling](../errors.md).
+See [Errors Handling](errors.md).
 
 ### Security
 
@@ -128,7 +128,7 @@ Use the `security` attribute in the `ApiResource` and `ApiProperty` attributes.
 
 Note you can also use the `security.yml` file if you only need to limit access to specific roles.
 
-See [Security](../security.md).
+See [Security](security.md).
 
 ### API versioning
 
@@ -142,4 +142,4 @@ See [API versioning](https://github.com/FriendsOfSymfony/FOSRestBundle/blob/3.x/
 
 API Platform has no native support to API versioning, but instead provides an approach consisting of deprecating resources when needed. It allows a smoother upgrade for clients, as they need to change their code only when it is necessary.
 
-See [Deprecating Resources and Properties](../deprecations.md).
+See [Deprecating Resources and Properties](deprecations.md).