Merge pull request LambdaTest#973 from amanchopra1905/stage

updated the masking docs and updated from '”' to '"'

Author: Ishavyas9

docs/advanced-tunnel-features.md

@@ -118,7 +118,7 @@ Key: 123456789abcdefghijklmnopqrstuv
 TunnelName: LambdaTest
 ```
 
-> **Note:** You will need to replace this file with your credentials and it has to be named exactly “`.lt.yaml`“. Once you specify the proxy information as environment variable, it gets auto detected.
+> **Note:** You will need to replace this file with your credentials and it has to be named exactly "`.lt.yaml`". Once you specify the proxy information as environment variable, it gets auto detected.
 
 Similarly, you can go ahead and pass any other variables by just specifying them in the YAML file. For example, if you wish to have verbose variable passed on for detailed logs while the binary is being configured. You will add the verbose flag in your YAML file:
 

docs/app-center-integration.md

@@ -82,13 +82,13 @@ Before getting started with the setup, you would need access to the following:
 
   ***
 
-2. Click on the “User API Tokens” to generate a token.
+2. Click on the "User API Tokens" to generate a token.
 
   <img loading="lazy" src={require('../assets/images/app-center-integration/app-center02.webp').default} alt="cmd" className="doc_img"/>
 
   ***
 
-3. Click on “Add new API token” to add the new token.
+3. Click on "Add new API token" to add the new token.
 
   <img loading="lazy" src={require('../assets/images/app-center-integration/app-center03.webp').default} alt="cmd" className="doc_img"/>
 
@@ -104,7 +104,7 @@ Before getting started with the setup, you would need access to the following:
 
 ---
 
-1. Click on the “Configure” Button
+1. Click on the "Configure" Button
 
   <img loading="lazy" src={require('../assets/images/app-center-integration/app-center05.webp').default} alt="cmd" className="doc_img"/>
 
@@ -116,7 +116,7 @@ Before getting started with the setup, you would need access to the following:
 
   ***
 
-3. Now Select your Builds on App Center by clicking on “Select Builds” to Select the “Builds” from App Center.
+3. Now Select your Builds on App Center by clicking on "Select Builds" to Select the "Builds" from App Center.
 
   <img loading="lazy" src={require('../assets/images/app-center-integration/app-center07.webp').default} alt="cmd" className="doc_img"/>
 

docs/appium-app-performance.md

@@ -52,7 +52,7 @@ LambdaTest provides you with two metrics in a time-series format representing th
 
 1. **System CPU Usage (%)**: The total percentage of CPU being used by the entire system
 
-2. **App CPU Usage (%)**: The share of “System CPU usage” being used by the AUT.
+2. **App CPU Usage (%)**: The share of "System CPU usage" being used by the AUT.
 
 ***
 

docs/appium-appletv.md

@@ -253,13 +253,13 @@ if __name__ == "__main__":
 You can update your custom capabilities in test scripts. In this sample project, we are passing platform name, platform version, device name and app url (generated earlier) along with other capabilities like build name and test name via capabilities object. The capabilities object in the sample code are defined as:
 
 **Supported Model:**
-- Device: `"Apple TV"` ; OS Version:`“16"`
+- Device: `"Apple TV"` ; OS Version:`"16"`
 
 **Supported Capabilities:**
 Same as iOS
 
 **Platform:**
-`”tvOS"`
+`"tvOS"`
 
 ```python title="appletv.py"
 def getCaps():

docs/appium-firetv.md

@@ -231,13 +231,13 @@ if __name__ == "__main__":
 You can update your custom capabilities in test scripts. In this sample project, we are passing platform name, platform version, device name and app url (generated earlier) along with other capabilities like build name and test name via capabilities object. The capabilities object in the sample code are defined as:
 
 **Supported Model:**
-- Device: `"Amazon Fire TV Stick"` ; OS Version:`“7"`
+- Device: `"Amazon Fire TV Stick"` ; OS Version:`"7"`
 
 **Supported Capabilities:**
 Same as Android.
 
 **Platform:**
-`”fireos"`
+`"fireos"`
 
 ```python title="firetv.py"
 def getCaps():

docs/appium-ios-app-settings.md

@@ -90,7 +90,7 @@ Currently, App Automate supports the following permission settings:
 
 One important thing to remember while handling Permission Settings is that, we have to first take action on the **Permission Pop ups** from the app when they appear and then only those particular Permission Settings will be reflected in the app settings page. For example:
 
-Let's say we pass Camera: “On“ in the lambda hook’s preferences even before handling Camera’s permission popup from the app, the Camera key would be missing on the app settings page which would result in failure. So we have to be sure that we have handled the permission pop ups before calling lambda hook.
+Let's say we pass Camera: "On" in the lambda hook’s preferences even before handling Camera’s permission popup from the app, the Camera key would be missing on the app settings page which would result in failure. So we have to be sure that we have handled the permission pop ups before calling lambda hook.
 
 :::info
 
@@ -122,7 +122,7 @@ Currently, App Automate supports the following custom settings:
 
 Apart from Textfields and Sliders, for every other settings, we have to pass the Name of that particular setting as the **key-value pair**. For example:
 
-- “Reset App“ : “On“.
+- "Reset App" : "On".
 
 For **textfields and sliders**, we pass the index of that particular textfield or slider starting from 1 when we traverse from top to bottom. For example:
 

docs/appium-rokutv.md

@@ -226,14 +226,14 @@ if __name__ == "__main__":
 You can update your custom capabilities in test scripts. In this sample project, we are passing platform name, platform version, device name and app url (generated earlier) along with other capabilities like build name and test name via capabilities object. The capabilities object in the sample code are defined as:
 
 **Supported Model:**
-- Device: `"Roku Ultra"` ; OS Version:`“11"`
-- Device: `"Roku Express"` ; OS Version:`“11"`
+- Device: `"Roku Ultra"` ; OS Version:`"11"`
+- Device: `"Roku Express"` ; OS Version:`"11"`
 
 **Supported Capabilities:**
 Please check at the end of the doc.
 
 **Platform:**
-`”roku"`
+`"roku"`
 
 ```python title="main.py"
     caps = {

docs/appveyor-ci-integration.md

@@ -59,7 +59,7 @@ To perform your tests with LambdaTest, you would need the below things to be alr
 
 2.  You also need your LambdaTest authentication credentials, which include your LambdaTest username, and access key.
 
-> To get your Username and Access Key, go to your [LambdaTest automation dashboard](https://automation.lambdatest.com/) and click on the “key” icon left to the help button, on the top right corner. <img loading="lazy" src={require('../assets/images/uploads/profile-1.webp').default} alt="appveyor ci integration" width="462" height="325" className="doc_img"/>
+> To get your Username and Access Key, go to your [LambdaTest automation dashboard](https://automation.lambdatest.com/) and click on the "key" icon left to the help button, on the top right corner. <img loading="lazy" src={require('../assets/images/uploads/profile-1.webp').default} alt="appveyor ci integration" width="462" height="325" className="doc_img"/>
 
 Update your username and access key in the "Config.properties" file.
 
@@ -90,9 +90,9 @@ Below is the step-by-step execution of the AppVeyor CI pipeline.
 1.  Make sure to add your LambdaTest's hub URL and [Desired Capabilities](/docs/selenium-automation-capabilities/) in your test setup, as done in the _AppveyorCI/src/main/java/stepDefinitions/ToDoStepDefinition.java_ file of the mentioned GitHub repository.
 
 2.  Push the changes to your integrated GitHub repository. For example, we have changed the test name in the forked repository.
-3.  Once the edit is complete, click on “Commit Changes” to save and commit the changes made. AppVeyor CI is activated as soon as this step is done since we have used “push event” for triggering the AppVeyor CI. <img loading="lazy" src={require('../assets/images/uploads/appveyorCi-10-1024x417.webp').default} alt="appveyor ci integration" width="768" height="313" className="doc_img"/>
+3.  Once the edit is complete, click on "Commit Changes" to save and commit the changes made. AppVeyor CI is activated as soon as this step is done since we have used "push event" for triggering the AppVeyor CI. <img loading="lazy" src={require('../assets/images/uploads/appveyorCi-10-1024x417.webp').default} alt="appveyor ci integration" width="768" height="313" className="doc_img"/>
 
-4.  As soon as the AppVeyor CI is triggered (through push event in this case), a new build can be seen in the “Timeline” on your [LambdaTest's automation dashboard](https://automation.lambdatest.com/timeline/). The current status of this build will be “running” or “executing”. <img loading="lazy" src={require('../assets/images/uploads/appveyorCi-11-1024x460.webp').default} alt="appveyor ci integration" width="768" height="345" className="doc_img"/>
+4.  As soon as the AppVeyor CI is triggered (through push event in this case), a new build can be seen in the "Timeline" on your [LambdaTest's automation dashboard](https://automation.lambdatest.com/timeline/). The current status of this build will be "running" or "executing". <img loading="lazy" src={require('../assets/images/uploads/appveyorCi-11-1024x460.webp').default} alt="appveyor ci integration" width="768" height="345" className="doc_img"/>
 
 5.  Now based on the tests, this build can pass or fail. If passed, a green tick along with the term **Passed** will appear in the summary of the test. Else if failed, a red cross will appear instead, along with the term **Failed**, as shown below.<img loading="lazy" src={require('../assets/images/uploads/appveyorCi-12-1024x462.webp').default} alt="appveyor ci integration" width="768" height="347" className="doc_img"/>
 

docs/automation-testing-using-jasmine-with-karma.md

@@ -186,7 +186,7 @@ customLaunchers: { chrome: {
         tunnel: true, // In case karma is running on local machine
     }   }
 ```
-> **Important Note**: Some Safari & IE browsers don’t support automatic resolution of the URL string “localhost”. Therefore if you test on URLs like "`http://localhost/`" or "`http://localhost:8080`" etc, you would get an error in these browsers. A possible solution is to use "`localhost.lambdatest.com`" or replace the string “localhost” with machine IP address. For example, if you wanted to test "`http://localhost/dashboard`" or, and your machine IP is 192.168.2.6 you can instead test on "`http://192.168.2.6/dashboard`" or "`http://localhost.lambdatest.com/dashboard`".
+> **Important Note**: Some Safari & IE browsers don’t support automatic resolution of the URL string "localhost". Therefore if you test on URLs like "`http://localhost/`" or "`http://localhost:8080`" etc, you would get an error in these browsers. A possible solution is to use "`localhost.lambdatest.com`" or replace the string "localhost" with machine IP address. For example, if you wanted to test "`http://localhost/dashboard`" or, and your machine IP is 192.168.2.6 you can instead test on "`http://192.168.2.6/dashboard`" or "`http://localhost.lambdatest.com/dashboard`".
 
 ## Avoid Timeouts With psuedoActivityInternal
 * * *

docs/aws-codepipeline-with-hyperexecute.md

@@ -111,11 +111,11 @@ phases:
         command: ./hyperexecute --user <your_user_name> --key <your_access_key> --config <your_yaml_file>
 ```
 
-- In the **buildspec** specification, choose the first option - **“Use a buildspec file”**.
+- In the **buildspec** specification, choose the first option - **"Use a buildspec file"**.
 
-- Now Click the **“continue to code pipeline”** button and then click on **Next**.
+- Now Click the **"continue to code pipeline"** button and then click on **Next**.
 
-- You can “**Skip deploy stage”** and finally click **“Create Pipeline”** button.
+- You can "**Skip deploy stage"** and finally click **"Create Pipeline"** button.
 
 <img loading="lazy" src={require('../assets/images/hyperexecute/integration/ci-cd/aws/STEP4.webp').default} alt="Image"  className="doc_img"/>