Merge pull request #8553 from msm1992/master-remove$

Remove $ from commands

en/docs/install-and-setup/setup/api-controller/advanced-topics/configuring-git-integration.md

@@ -15,7 +15,7 @@ After the project deletion is enabled, any deleted API/Application or API Produc
 
 !!! example
     ```bash
-    $ apictl vcs deploy -e dev
+    apictl vcs deploy -e dev
     Deploying Projects (1)...
 
     APIs (1) ...
@@ -88,7 +88,7 @@ apictl set --vcs-config-path <full-path-to-store-vcs_config.yaml>
 
 !!! example
     ```bash
-    $ apictl set --vcs-config-path /home/wso2/api-manager/gitconfigs
+    apictl set --vcs-config-path /home/wso2/api-manager/gitconfigs
     VCS config file path is set to : /home/wso2/api-manager/gitconfigs
     ```
 

en/docs/install-and-setup/setup/api-controller/advanced-topics/using-dynamic-data-in-api-controller-projects.md

@@ -181,10 +181,10 @@ For example, consider we need to send a special header to the backend when calli
 6. Generate a token and invoke the API
 
     ```bash
-    $ apictl get keys -e development -n SwaggerPetstore -v 1.0.6 -r admin
+    apictl get keys -e development -n SwaggerPetstore -v 1.0.6 -r admin
     eyJ0eXAiOiJKV1QiLCJhbGciOiJSUz....RWrACAUNSFBpxz1lRLqFlDiaVJAg
 
-    $ curl -H "Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJSUz....RWrACAUNSFBpxz1lRLqFlDiaVJAg" https://localhost:8243/v2/1.0.6/pet/1 -k
+    curl -H "Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJSUz....RWrACAUNSFBpxz1lRLqFlDiaVJAg" https://localhost:8243/v2/1.0.6/pet/1 -k
     {"id":1,"category":{"id":1001,"name":"Animal"},"name":"doggie","photoUrls":["img/test/dog.jpeg","img/test/dog1.jpeg"],"tags":[{"id":2001,"name":"Pet"},{"id":2002,"name":"Animal"}],"status":"available"}
     ```
 

en/docs/install-and-setup/setup/api-controller/building-jenkins-ci-cd-pipeline.md

@@ -76,8 +76,8 @@ Now let’s initialize the source repository. This will be done from the develop
 1. Clone the source repository. Navigate to the repository folder.
 
     ```
-    $ git clone https://github.com/chamilaadhi/poc-cicd-source-repo.git
-    $ cd poc-cicd-source-repo
+    git clone https://github.com/chamilaadhi/poc-cicd-source-repo.git
+    cd poc-cicd-source-repo
     ```
 
 2. Execute the following command.
@@ -116,8 +116,8 @@ Deployment repository will be used to gather configurations for each deployment.
     Try uploading a sample resource. An example is given below.
 
     ```
-    $ touch resource.txt
-    $ curl -u repouser:<password> -X PUT https://xxxx.jfrog.io/artifactory/myrepo/ -T resource.txt
+    touch resource.txt
+    curl -u repouser:<password> -X PUT https://xxxx.jfrog.io/artifactory/myrepo/ -T resource.txt
     ```
 
     Access the repository URL to see the resource.
@@ -224,8 +224,8 @@ The artifact deployment job will listen to any new updates in the Artifactory re
 
 3. To test whether the webhook between Artifactory and the Jenkins job is working, you could execute the same upload test we did under Setup JFrog Artifactory section
   ```
-  $ touch resource.txt
-  $ curl -u repouser:<password> -X PUT https://xxxxx.jfrog.io/artifactory/myrepo/ -T resource.txt
+  touch resource.txt
+  curl -u repouser:<password> -X PUT https://xxxxx.jfrog.io/artifactory/myrepo/ -T resource.txt
   ```
 
 If the configuration is working, this will trigger a new build.

en/docs/install-and-setup/setup/api-controller/cicd-using-cli.md

@@ -225,8 +225,8 @@ The repositories (**Source** and **Deployment**) that you committed the project
 
 1. Set the Source and the Deployment directory paths.
    ```bash
-   $ apictl set --vcs-source-repo-path path/to/Source
-   $ apictl set --vcs-deployment-repo-path path/to/Deployment
+   apictl set --vcs-source-repo-path path/to/Source
+   apictl set --vcs-deployment-repo-path path/to/Deployment
    ```
 
     !!! note
@@ -238,14 +238,14 @@ The repositories (**Source** and **Deployment**) that you committed the project
 
 2.  Navigate to the Source directory.
     ```bash
-    $ cd path/to/Source
+    cd path/to/Source
     ```
 
 3.  As this is the first time that the Source repository is used for Git Integration functionality of apictl, run `vcs init` command to initialize the repository with apictl. This needs to run only once for the repository.
 
     !!! example
         ```bash
-        $ apictl vcs init
+        apictl vcs init
         Successfully initialized GIT repository
         ```
 
@@ -262,7 +262,7 @@ The repositories (**Source** and **Deployment**) that you committed the project
 
     !!! example
         ```bash
-        $ apictl vcs status -e prod
+        apictl vcs status -e prod
         Projects to Deploy (1)
 
         APIs (1) ...
@@ -281,7 +281,7 @@ The repositories (**Source** and **Deployment**) that you committed the project
 
     !!! example
         ```bash
-        $ apictl vcs deploy -e prod
+        apictl vcs deploy -e prod
         Deploying Projects (1)...
 
         APIs (1) ...
@@ -295,7 +295,7 @@ The repositories (**Source** and **Deployment**) that you committed the project
 
     !!! example
         ```bash
-        $ apictl vcs deploy -e prod
+        apictl vcs deploy -e prod
         Everything is up-to-date
         ```
 
@@ -312,7 +312,7 @@ The repositories (**Source** and **Deployment**) that you committed the project
     4.  Navigate to the Source repository and run `vcs status` command to verify the new project addition (You can do the same by navigating to the Deployment repository as well).
 
         ```bash
-        $ apictl vcs status -e prod
+        apictl vcs status -e prod
         Projects to Deploy (1)
 
         APIs (1) ...
@@ -322,7 +322,7 @@ The repositories (**Source** and **Deployment**) that you committed the project
     5.  Run `vcs deploy` command to deploy the new API to the production environment.
 
         ```bash
-        $ apictl vcs deploy -e prod
+        apictl vcs deploy -e prod
         Deploying Projects (1)...
 
         APIs (1) ...
@@ -464,7 +464,7 @@ For example, let us consider there is an [API Product]({{base_path}}/design/crea
 1.  Export the API Product using `export api-product` command from the development environment (dev). For more information, see [Export an API Product]({{base_path}}/install-and-setup/setup/api-controller/managing-apis-api-products/migrating-api-products-to-different-environments/#export-an-api-product).
 
     ```bash
-    $ apictl export api-product -n PetsInfo -v 1.0.0 -e dev --latest
+    apictl export api-product -n PetsInfo -v 1.0.0 -e dev --latest
     
     Successfully exported API Product!
     Find the exported API Product at /home/wso2user/.wso2apictl/exported/api-products/dev/PetsInfo_1.0.0.zip
@@ -480,7 +480,7 @@ For example, let us consider there is an [API Product]({{base_path}}/design/crea
 
     !!! example
         ```bash
-        $ apictl vcs status -e prod
+        apictl vcs status -e prod
         Projects to Deploy (1)
 
         API Products (1) ...
@@ -491,7 +491,7 @@ For example, let us consider there is an [API Product]({{base_path}}/design/crea
         If you haven't initialized the repository with API Controller, you will get the below error.
 
         ```bash
-        $ apictl vcs status -e prod
+        apictl vcs status -e prod
         apictl: The repository info: vcs.yaml is not found in the repository root. If this is the first time you are using this repo, please initialize it with 'vcs init'.
         Exit status 1
         ```
@@ -502,7 +502,7 @@ For example, let us consider there is an [API Product]({{base_path}}/design/crea
 
     !!! example
         ```bash
-        $ apictl vcs deploy -e prod
+        apictl vcs deploy -e prod
         Deploying Projects (1)...
 
         API Products (1) ...
@@ -564,7 +564,7 @@ Let us assume that the **PetsApp** application is in the development environment
 1.  Export the Application using the `export app` command from the development environment (dev). Note that `--with-keys` option is used to export the subscriptions and keys (if any) of the application.
 
     ```bash
-    $ apictl export app --name PetsApp --owner david -e dev --with-keys
+    apictl export app --name PetsApp --owner david -e dev --with-keys
 
     Successfully exported Application!
     Find the exported Application at /home/wso2user/.wso2apictl/exported/apps/dev/david_PetsApp.zip
@@ -579,7 +579,7 @@ Let us assume that the **PetsApp** application is in the development environment
 
     !!! example
         ```bash
-        $ apictl vcs status -e prod
+        apictl vcs status -e prod
         Projects to Deploy (1)
 
         Applications (1) ...
@@ -590,7 +590,7 @@ Let us assume that the **PetsApp** application is in the development environment
         If you haven't initialized the repository with API Controller, you will get the below error.
         
         ```bash
-        $ apictl vcs status -e prod
+        apictl vcs status -e prod
         apictl: The repository info: vcs.yaml is not found in the repository root. If this is the first time you are using this repo, please initialize it with 'vcs init'.
         Exit status 1
         ```
@@ -601,7 +601,7 @@ Let us assume that the **PetsApp** application is in the development environment
 
     !!! example
         ```bash
-        $ apictl vcs deploy -e prod
+        apictl vcs deploy -e prod
         Deploying Projects (1)...
 
         Applications (1) ...

en/docs/install-and-setup/setup/mi-setup/transport_configurations/configuring-transports.md

@@ -107,7 +107,7 @@ listener.parameter.PreferredCiphers = "TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,T
 !!! Note
     To check the above configuration changes related to SSL. Download [testsslserver.jar](https://docs.wso2.com/download/attachments/53125465/testsslserver.jar?version=1&modificationDate=1471859455000&api=v2) and test with the following command.
 
-    $ java -jar testsslserver.jar localhost 8253
+    java -jar testsslserver.jar localhost 8253
 
 ## Configuring the VFS transport
 

en/docs/install-and-setup/setup/security/configuring-transport-level-security.md

@@ -35,7 +35,7 @@ To prevent these types of security attacks, it is encouraged to disable the weak
         -   When you use the supported cipher suites listed [here](https://docs.wso2.com/display/ADMIN44x/Supported+Cipher+Suites), the BEAST attack status will be shown as vulnerable. Note that this is a client-side vulnerability caused by the TLSv1 protocol. You can make the BEAST status protected by removing TLSv1, which will make clients with TLSv1 unusable. Therefore, it is recommended tofixed this from the client side.
 
         ``` java
-        $ java -jar testsslserver.jar localhost 9443
+        java -jar testsslserver.jar localhost 9443
         ```
 
 !!! info

en/docs/install-and-setup/setup/security/enabling-java-security-manager.md

@@ -32,13 +32,13 @@ The steps below show how to enable the Java Security Manager for WSO2 products.
     First, export the `signFiles` public key certificate from the `signkeystore.jks` keystore by executing the following command:
 
     ```java
-    $ keytool -export -keystore signkeystore.jks -alias signFiles -file sign-cert.cer 
+    keytool -export -keystore signkeystore.jks -alias signFiles -file sign-cert.cer 
     ```
 
     Then, import the same `signFiles` certificate to the `wso2carbon.jks` keystore by executing the command given below. Be sure to specify the correct directory path to the `wso2carbon.jks` file of your product.
 
     ```bash
-    $ keytool -import -alias signFiles -file sign-cert.cer -keystore <PATH_to_API-M_HOME>/repository/resources/security/wso2carbon.jks
+    keytool -import -alias signFiles -file sign-cert.cer -keystore <PATH_to_API-M_HOME>/repository/resources/security/wso2carbon.jks
     Enter keystore password:  
     Owner: CN=John, OU=Engineering, O=WSO2, L=Colombo, ST=Western, C=LK
     Issuer: CN=John, OU=Engineering, O=WSO2, L=Colombo, ST=Western, C=LK