improve content and readability (#6355)

Author: letzya

CONTRIBUTING-TECHNICAL-GUIDE.md

@@ -14,34 +14,34 @@ GH provides great DX for making updates, committing and creating PRs via the bro
 Use GitHub GUI browser when you:
 - Have simple and only a few edits of the markdown files. 
 - Already know the syntax for adding internal links and adding images. 
-- Already know what you are going to write and you **don't** need many iterative commits to see if the result looks okay. In this case, using a local environment will be much faster (explain in the next section)
+- Already know what you are going to write and you **don't** need many iterative commits to see if the result looks okay. In this case, using a local environment will be much faster as explained in the next section.
 
 #### How To Use It?
-Will briefly explain it as it is quite trivial:
+I'll briefly explain the process as it is quite straightforward:
 1. Via the GUI you can simply click the pencil icon to start editing, then check the differences, click commit to commit the changes to a new branch, and eventually create a PR. 
 2. Check that the CI jobs started running. These jobs run tests on the website including your changes. Running CI jobs are displayed in yellow. 
 3. Once the CI job finishes it will turn green. Upon completion, you will see a preview link that you should use to check your changes on a real deployment of the Tyk docs website.
 
 
 ### 2. Local Development Environment
-Local environment means, checking out the tyk-docs repo and updating the files using an editor or an IDE. This allows you to test the changes by running Hugo locally and check for errors in Hugo or in the website Hugo generated.
+Local environment means checking out the tyk-docs repo and updating the files using an editor or an IDE. This allows you to test your changes by running Hugo locally and check for errors both in the Hugo process and in the website that Hugo generates.
 
 #### When To Use It?
 Using the browser is not always enough and you sometimes need to check out the repo and work locally.
 You normally favor using a local environment when you need to:
-- Test things yourself before you push them
-- Repeatedly push changes and test the website
+- Test your changes in real-time before pushing them
+- Repeatedly make changes and test the website
 
-Doing so by **running Hugo locally will save you a lot of time** since it takes the CI a few minutes to update the deployment with the latest changes and finish its test before it becomes green. 
+Doing so by **running Hugo locally will save you a lot of time** since it takes the CI a few minutes to update the deployment with the latest changes and complete its tests before showing a green success status.
 
 #### Use Cases For Local Development Environment
 When you need to:
-- Test things yourself before you push them
-- Check that the image you added work
+- Preview changes and verify their appearance locally
+- Check that the images you added work correctly
 - See how images are rendered on the page
 - Check that the internal links you added work
-- Are not sure about the syntax of links or images when you work on many pages
-- When adding new files, it's easier to run it locally since you cannot be sure of the internal links format and may need to validate referenced links to other content pages and sections
+- When you are not sure about the syntax of links or images when working on many pages
+- When adding new files, it's easier to run Hugo locally because you need to validate the format of internal links and references to other content pages and sections
 
 #### How To Use It?
 
@@ -415,13 +415,15 @@ You can also specify a class or custom styling:
 ### Feature Name {{< pill-label text="LABEL" style="background-color: #f0f0f0; color: #333;" >}}
 ```
 
-For detailed examples and all available styling options, see the [pill-label examples page](content/ui-examples/test-pill-label.md). You can run Hugo locally to see how the pill labels appear in your browser:
+To read and view detailed examples of all the available styling options, see the [pill-label live examples page](https://tyk.io/docs/ui-examples/test-pill-label/)
+
+There's also a [security pill-label test file](./tyk-docs/tyk-docs/content/ui-examples/test-pill-label-security.md) to validate the security of the implementation. It's in a draft mode, so if you want to see it in the website, you need to run Hugo with `--buildDrafts` as follows
 
 ```
-hugo server --theme=tykio --buildDrafts --enableGitInfo
+hugo server --theme=tykio --buildDrafts --enableGitInfo --port 1313
 ```
 
-Then navigate to `http://localhost:1313/docs/nightly/ui-examples/test-pill-label/` to view the examples.
+Then navigate to `http://localhost:1313/docs/nightly/ui-examples/test-pill-label-security/` to view the examples.
 
 ## License