docs: added dividers + see also section (#2899)

docs/content/usage/local-development.md

@@ -14,6 +14,8 @@ Whether you want to implement something differently, introduce a new future as p
 
 All the packages are part of a [Yarn workspace](https://classic.yarnpkg.com/lang/en/docs/workspaces/). So, when you run a command in the root of the project, such as `yarn build`, it goes through all registered packages in the workspace under the `packages` directory and runs the `build` command in each of those packages.
 
+---
+
 ## Prerequisites
 
 ### Yarn
@@ -51,6 +53,8 @@ In the directory of your forked GitHub repository, run the following command to
 medusa-dev --set-path-to-repo `pwd`
 ```
 
+---
+
 ## Run Tests in the Repository
 
 In this section, you’ll learn how to run tests in the Medusa repository. This is helpful after you customize any of Medusa’s packages and want to make sure everything is still working as expected.
@@ -94,6 +98,8 @@ To run the plugin integration tests, run the following command in the root direc
 yarn test:integration:plugins
 ```
 
+---
+
 ## Test in a Local Server
 
 Using Medusa’s dev CLI tool, you can test any changes you make to Medusa’s packages in a local server installation. This eliminates the need to publish these packages on NPM publicly to be able to use them.
@@ -146,7 +152,9 @@ medusa-dev -q
 medusa-dev --packages @medusajs/medusa-cli medusa-file-minio
 ```
 
-## What’s Next
+---
 
-- Check out our [contribution guidelines](https://github.com/medusajs/medusa/blob/master/CONTRIBUTING.md).
-- Learn how to [create a plugin](../advanced/backend/plugins/create.md).
+## See Also
+
+- [Create a Plugin](../advanced/backend/plugins/create.md)
+- [Contribution Guidelines](https://github.com/medusajs/medusa/blob/master/CONTRIBUTING.md)