fix: update links

Author: RomanHotsiy

template/README.md.ejs

@@ -20,10 +20,10 @@ Validates the definition.
 
 ## Contribution Guide
 
-Below is a sample contribution guide. The tools 
-in the repository don't restrict you to any 
+Below is a sample contribution guide. The tools
+in the repository don't restrict you to any
 specific structure. Adjust the contribution guide
-to match your own structure. However, if you 
+to match your own structure. However, if you
 don't have a structure in mind, this is a
 good place to start.
 
@@ -32,8 +32,8 @@ adjust the file/folder organization.
 
 The `.redocly.yaml` controls settings for various
 tools including the lint tool and the reference
-docs engine.  Open it to find examples and 
-[read the docs](https://docs.redoc.ly/cli/configuration/)
+docs engine.  Open it to find examples and
+[read the docs](https://redoc.ly/docs/cli/configuration/)
 for more information.
 
 

template/openapi/README.md

@@ -6,7 +6,7 @@ That file contains references to the entire API definition.
 
 Here are some sections to pay attention to:
 
-* Top-level **description**: this accepts markdown, and Redoc and Redocly API Reference will render it at the top of the docs.  Consider maintaining your markdown in a separate file and [embedding it](https://docs.redoc.ly/api-reference-docs/embedded-markdown/). Note to Redoc community edition users, the special tags are only available to the Redocly API Reference users, but you can still embed markdown.
+* Top-level **description**: this accepts markdown, and Redoc and Redocly API Reference will render it at the top of the docs.  Consider maintaining your markdown in a separate file and [embedding it](https://redoc.ly/docs/api-reference-docs/embedded-markdown/). Note to Redoc community edition users, the special tags are only available to the Redocly API Reference users, but you can still embed markdown.
 * Security schemes: you will define the scheme(s) your API uses for security (eg OAuth2, API Key, etc...). The security schemes are used by the Redocly API Reference "Try It" API console feature.
 * [Paths](paths/README.md): this defines each endpoint.  A path can have one operation per http method.
 * Tags: it's a good idea to organize each operation.  Each tag can have a description.  The description is used as a section description within the reference docs.