From 9ab1ac682aaf870b36c1f03244c2129df6732eb3 Mon Sep 17 00:00:00 2001
From: Shivam7-1 <55046031+Shivam7-1@users.noreply.github.com>
Date: Thu, 8 Oct 2020 12:05:24 +0530
Subject: [PATCH] Updated quickstart.md typos

---
 content/actions/quickstart.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/actions/quickstart.md b/content/actions/quickstart.md
index ed384ae4fdcd..f07385b9e4c4 100644
--- a/content/actions/quickstart.md
+++ b/content/actions/quickstart.md
@@ -74,6 +74,6 @@ Committing the workflow file in your repository triggers the `push` event and ru
 
 The super-linter workflow you just added runs any time code is pushed to your repository to help you spot errors and inconsistencies in your code. But, this is only the beginning of what you can do with {% data variables.product.prodname_actions %}. Your repository can contain multiple workflows that trigger different jobs based on different events. {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_actions %}:
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial
-- "[Guides](/actions/guides)" for specific uses cases and examples
-- [github/super-linter](https://github.com/github/super-linter) for more details about configuring the Super-Linter action
+- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial.
+- "[Guides](/actions/guides)" for specific uses cases and examples.
+- [github/super-linter](https://github.com/github/super-linter) for more details about configuring the Super-Linter action.