Merge pull request #2287 from takahashim/fix-links-in-docs

fix broken links in Guide

docs/01-guide/03-deploying-services.md

@@ -34,7 +34,7 @@ If you want to deploy to different stages and regions later on, provide correspo
 For example, deploy to the `production` stage in the `eu-central-1` region by running a `deploy` command that looks like
 this: `serverless deploy --stage production --region eu-central-1`.
 
-Check out the [deploy command docs](../03-cli-reference/02-deploy.md) for all the details and options.
+Check out the [deploy command docs](../03-cli-reference/03-deploy.md) for all the details and options.
 
 ## Conclusion
 

docs/01-guide/04-invoking-functions.md

@@ -23,7 +23,7 @@ As a result of this you should see the functions message printed out on the cons
 
 You can also change the message returned by your function in `handler.js` or change the event.json file to see how your function output will change.
 
-You can also check out the [invoke command docs](../03-cli-reference/03-invoke.md) for all the details and options.
+You can also check out the [invoke command docs](../03-cli-reference/04-invoke.md) for all the details and options.
 
 ## Viewing Function Logs
 
@@ -38,7 +38,7 @@ By default, Serverless will fetch all the logs that happened in the past 30 minu
 The logs will then be displayed on your terminal. By default, AWS logs a `START`, `END` & `REPORT` logs for each invocation, plus of course any logging functionality you have in your code. You should see all these logs on the screen.
 
 The logs command provides different options you can use. Please take a look at the
-[logs command documentation](../03-cli-reference/04-logs.md) to see what else you can do.
+[logs command documentation](../03-cli-reference/05-logs.md) to see what else you can do.
 
 ## Conclusion