Fixen broken doc links

docs/development/code-review-guidelines/README.md

@@ -46,7 +46,7 @@ Every developer and reviewer should read the Rails Security Guide.
 
 ## Other
 
-- For external contributions: Check whether the author has signed a [Contributor License Agreement](../development/#openproject-contributor-license-agreement-cla) and kindly ask for it if not.
+- For external contributions: Check whether the author has signed a [Contributor License Agreement](../#openproject-contributor-license-agreement-cla) and kindly ask for it if not.
 - Copyright notice: When new files are added, make sure they contain the OpenProject copyright notice (copy from any file in OpenProject).
 - Adding Gems: When adding gems, make sure not only the Gemfile is updated, but also the Gemfile.lock.
 - No trailing whitespace.

docs/development/product-development-handbook/README.md

@@ -64,7 +64,7 @@ For a guideline on how to report feature requests, refer to the [Feature request
 
 In regular intervals (e.g. once a week), PMs screen the requirements added to the Wish List and evaluate them:
 
-1. PM adjusts feature requests to a common format (see [Feature Request guideline]([https://docs.openproject.org/development/submit-feature-idea](https://docs.openproject.org/development/submit-feature-idea/)/)). 
+1. PM adjusts feature requests to a common format (see [Feature Request guideline](https://docs.openproject.org/development/submit-feature-idea/)). 
 2. PM rejects duplicated feature requests with a reference to the original feature requests.
 3. PM sets RICE values and a RICE score for feature requests.
 4. PM creates an Opportunity Canvas for requirements with a moderate to high level of uncertainty (> 80%) or for large requirements (effort > 1 week).