Merge pull request #479 from eliheron/update-partials

update partials

docs/BUILD_TEMPLATE.md

@@ -187,7 +187,7 @@ npm install twilio-video -w=video-token
 
 ### Adding environment variables
 
-Function templates can use environment variables for deploy-specific secrets by adding them to the `.env` file in the root of your template. These are the fields that the user will be able to pre-set on the CodeExchange web app. `Step 2` visually shows the env vars that are set in `.env`: <https://www.twilio.com/code-exchange/simple-sms-forwarding>
+Function templates can use environment variables for deploy-specific secrets by adding them to the `.env` file in the root of your template. These are the fields that the user will be able to pre-set on the CodeExchange web app. `Step 2` visually shows the env vars that are set in `.env`: [https://www.twilio.com/code-exchange/simple-sms-forwarding](https://www.twilio.com/code-exchange/simple-sms-forwarding)
 
 Any variable you want the user to have to set should be added to the `.env.example` file in your template directory and should include a commented line before that explaining what the variable is about. Example:
 

docs/CONTRIBUTING.md

@@ -18,7 +18,7 @@ If this is your first time contributing to an open-source project, [check out ou
 
 Under the hood, every CodeExchange Quick Deploy app is powered by a Function Template.
 
-See Quick Deploy apps here: <https://www.twilio.com/code-exchange?q=&f=serverless>
+See Quick Deploy apps here: [https://www.twilio.com/code-exchange?q=&f=serverless](https://www.twilio.com/code-exchange?q=&f=serverless)
 
 ## Setting up your local environment
 

docs/TESTING.md

@@ -136,7 +136,7 @@ If you want to test how your new template works with the Twilio CLI, make sure y
 
 Afterwards make sure you push your changes to a different branch or fork of the repository. Your changes have to be uploaded to GitHub for you to be able to test them.
 
-For example if I'm working on the `verify` template, I might push my changes to a new branch called `update-verify` under my personal fork of the `function-templates` repository, located at: <https://github.com/dkundel/function-templates>.
+For example if I'm working on the `verify` template, I might push my changes to a new branch called `update-verify` under my personal fork of the `function-templates` repository, located at: [https://github.com/dkundel/function-templates](https://github.com/dkundel/function-templates).
 
 In order to test if my changes are working, I can invoke the `twilio serverless:init` command with the following flags: