Update access-token.md

Author: MichaelCurrin

recipes/ci-cd/github-actions/tokens/access-token.md

@@ -1,5 +1,6 @@
 # Access token cheatsheet
 
+{% raw %}
 
 ## Warning
 
@@ -38,7 +39,6 @@ Github will also scan to find accidentally committed secrets - [doc](https://hel
 
 ## How to use an access token in a workflow
 
-
 ### 1. Create token
 
 1. Go to **Personal Access Tokens** section.
@@ -53,7 +53,6 @@ Github will also scan to find accidentally committed secrets - [doc](https://hel
    to commit to the `gh-pages` branch.
 1. **Copy** the token value.
 
-
 ### 2. Set the token in secrets
 
 1. Go to your repository's **Settings*
@@ -123,3 +122,5 @@ https://<token>:[email protected]/USERNAME/REPO_NAME.git
 From [blog post](https://github.blog/2012-09-21-easier-builds-and-deployments-using-git-over-https-and-oauth/)
 
 > Tokens should be treated as passwords. Putting the token in the clone URL will result in Git writing it to the .git/config file in plain text. Unfortunately, this happens for HTTP passwords, too.
+
+{% endraw %}