docs(readme): remove www. from fastify.dev` urls

templates/app-esm/README.md

@@ -21,4 +21,4 @@ Run the test cases.
 
 ## Learn More
 
-To learn Fastify, check out the [Fastify documentation](https://www.fastify.dev/docs/latest/).
+To learn Fastify, check out the [Fastify documentation](https://fastify.dev/docs/latest/).

templates/app-esm/plugins/README.md

@@ -11,6 +11,6 @@ that will then be used in the rest of your application.
 
 Check out:
 
-* [The hitchhiker's guide to plugins](https://www.fastify.dev/docs/latest/Guides/Plugins-Guide/)
-* [Fastify decorators](https://www.fastify.dev/docs/latest/Reference/Decorators/).
-* [Fastify lifecycle](https://www.fastify.dev/docs/latest/Reference/Lifecycle/).
+* [The hitchhiker's guide to plugins](https://fastify.dev/docs/latest/Guides/Plugins-Guide/)
+* [Fastify decorators](https://fastify.dev/docs/latest/Reference/Decorators/).
+* [Fastify lifecycle](https://fastify.dev/docs/latest/Reference/Lifecycle/).

templates/app-esm/routes/README.md

@@ -7,7 +7,7 @@ to independently deploy some of those.
 In this folder you should define all the routes that define the endpoints
 of your web application.
 Each service is a [Fastify
-plugin](https://www.fastify.dev/docs/latest/Reference/Plugins/), it is
+plugin](https://fastify.dev/docs/latest/Reference/Plugins/), it is
 encapsulated (it can have its own independent plugins) and it is
 typically stored in a file; be careful to group your routes logically,
 e.g. all `/users` routes in a `users.js` file. We have added
@@ -21,7 +21,7 @@ and eventually extract them.
 
 If you need to share functionality between routes, place that
 functionality into the `plugins` folder, and share it via
-[decorators](https://www.fastify.dev/docs/latest/Reference/Decorators/).
+[decorators](https://fastify.dev/docs/latest/Reference/Decorators/).
 
 If you're a bit confused about using `async/await` to write routes, you would
-better take a look at [Promise resolution](https://www.fastify.dev/docs/latest/Reference/Routes/#promise-resolution) for more details.
+better take a look at [Promise resolution](https://fastify.dev/docs/latest/Reference/Routes/#promise-resolution) for more details.

templates/app-ts-esm/README.md

@@ -20,4 +20,4 @@ Run the test cases.
 
 ## Learn More
 
-To learn Fastify, check out the [Fastify documentation](https://www.fastify.dev/docs/latest/).
+To learn Fastify, check out the [Fastify documentation](https://fastify.dev/docs/latest/).

templates/app-ts-esm/src/plugins/README.md

@@ -11,6 +11,6 @@ that will then be used in the rest of your application.
 
 Check out:
 
-* [The hitchhiker's guide to plugins](https://www.fastify.dev/docs/latest/Guides/Plugins-Guide/)
-* [Fastify decorators](https://www.fastify.dev/docs/latest/Reference/Decorators/).
-* [Fastify lifecycle](https://www.fastify.dev/docs/latest/Reference/Lifecycle/).
+* [The hitchhiker's guide to plugins](https://fastify.dev/docs/latest/Guides/Plugins-Guide/)
+* [Fastify decorators](https://fastify.dev/docs/latest/Reference/Decorators/).
+* [Fastify lifecycle](https://fastify.dev/docs/latest/Reference/Lifecycle/).

templates/app-ts-esm/src/routes/README.md

@@ -7,7 +7,7 @@ to independently deploy some of those.
 In this folder you should define all the routes that define the endpoints
 of your web application.
 Each service is a [Fastify
-plugin](https://www.fastify.dev/docs/latest/Reference/Plugins/), it is
+plugin](https://fastify.dev/docs/latest/Reference/Plugins/), it is
 encapsulated (it can have its own independent plugins) and it is
 typically stored in a file; be careful to group your routes logically,
 e.g. all `/users` routes in a `users.js` file. We have added
@@ -21,4 +21,4 @@ and eventually extract them.
 
 If you need to share functionality between routes, place that
 functionality into the `plugins` folder, and share it via
-[decorators](https://www.fastify.dev/docs/latest/Reference/Decorators/).
+[decorators](https://fastify.dev/docs/latest/Reference/Decorators/).

templates/app-ts/README.md

@@ -20,4 +20,4 @@ Run the test cases.
 
 ## Learn More
 
-To learn Fastify, check out the [Fastify documentation](https://www.fastify.dev/docs/latest/).
+To learn Fastify, check out the [Fastify documentation](https://fastify.dev/docs/latest/).

templates/app-ts/src/plugins/README.md

@@ -11,6 +11,6 @@ that will then be used in the rest of your application.
 
 Check out:
 
-* [The hitchhiker's guide to plugins](https://www.fastify.dev/docs/latest/Guides/Plugins-Guide/)
-* [Fastify decorators](https://www.fastify.dev/docs/latest/Reference/Decorators/).
-* [Fastify lifecycle](https://www.fastify.dev/docs/latest/Reference/Lifecycle/).
+* [The hitchhiker's guide to plugins](https://fastify.dev/docs/latest/Guides/Plugins-Guide/)
+* [Fastify decorators](https://fastify.dev/docs/latest/Reference/Decorators/).
+* [Fastify lifecycle](https://fastify.dev/docs/latest/Reference/Lifecycle/).

templates/app-ts/src/routes/README.md

@@ -7,7 +7,7 @@ to independently deploy some of those.
 In this folder you should define all the routes that define the endpoints
 of your web application.
 Each service is a [Fastify
-plugin](https://www.fastify.dev/docs/latest/Reference/Plugins/), it is
+plugin](https://fastify.dev/docs/latest/Reference/Plugins/), it is
 encapsulated (it can have its own independent plugins) and it is
 typically stored in a file; be careful to group your routes logically,
 e.g. all `/users` routes in a `users.js` file. We have added
@@ -21,4 +21,4 @@ and eventually extract them.
 
 If you need to share functionality between routes, place that
 functionality into the `plugins` folder, and share it via
-[decorators](https://www.fastify.dev/docs/latest/Reference/Decorators/).
+[decorators](https://fastify.dev/docs/latest/Reference/Decorators/).

templates/app/README.md

@@ -20,4 +20,4 @@ Run the test cases.
 
 ## Learn More
 
-To learn Fastify, check out the [Fastify documentation](https://www.fastify.dev/docs/latest/).
+To learn Fastify, check out the [Fastify documentation](https://fastify.dev/docs/latest/).

templates/app/plugins/README.md

@@ -11,6 +11,6 @@ that will then be used in the rest of your application.
 
 Check out:
 
-* [The hitchhiker's guide to plugins](https://www.fastify.dev/docs/latest/Guides/Plugins-Guide/)
-* [Fastify decorators](https://www.fastify.dev/docs/latest/Reference/Decorators/).
-* [Fastify lifecycle](https://www.fastify.dev/docs/latest/Reference/Lifecycle/).
+* [The hitchhiker's guide to plugins](https://fastify.dev/docs/latest/Guides/Plugins-Guide/)
+* [Fastify decorators](https://fastify.dev/docs/latest/Reference/Decorators/).
+* [Fastify lifecycle](https://fastify.dev/docs/latest/Reference/Lifecycle/).

templates/app/routes/README.md

@@ -7,7 +7,7 @@ to independently deploy some of those.
 In this folder you should define all the routes that define the endpoints
 of your web application.
 Each service is a [Fastify
-plugin](https://www.fastify.dev/docs/latest/Reference/Plugins/), it is
+plugin](https://fastify.dev/docs/latest/Reference/Plugins/), it is
 encapsulated (it can have its own independent plugins) and it is
 typically stored in a file; be careful to group your routes logically,
 e.g. all `/users` routes in a `users.js` file. We have added
@@ -21,7 +21,7 @@ and eventually extract them.
 
 If you need to share functionality between routes, place that
 functionality into the `plugins` folder, and share it via
-[decorators](https://www.fastify.dev/docs/latest/Reference/Decorators/).
+[decorators](https://fastify.dev/docs/latest/Reference/Decorators/).
 
 If you're a bit confused about using `async/await` to write routes, you would
-better take a look at [Promise resolution](https://www.fastify.dev/docs/latest/Reference/Routes/#promise-resolution) for more details.
+better take a look at [Promise resolution](https://fastify.dev/docs/latest/Reference/Routes/#promise-resolution) for more details.