Merge pull request wso2#4 from gomathyk/master

make changes to getting started and setup

en/docs/getting-started/about-this-release.md

@@ -7,25 +7,25 @@ version **5.7.0,** and contains the following new features and
 enhancements:
 
 -   Support for [OpenID Connect backchannel
-    logout](/using-wso2-identity-server/openid-connect-single-logout) .
+    logout](../../using-wso2-identity-server/openid-connect-single-logout) .
 -   Support for [SAML frontchannel
-    logout](/tutorials/configuring-SAML-2.0-Web-SSO/) .
+    logout](../../tutorials/configuring-SAML-2.0-Web-SSO/) .
 -   Improvements for [product
-    observability](/using-wso2-identity-server/working-with-product-observability) .
+    observability](../../using-wso2-identity-server/working-with-product-observability) .
 -   Support for [X509 certificate-based
-    authentication](/connectors/configuring-x509-authenticator-with-ssl-termination)
+    authentication](../../connectors/configuring-x509-authenticator-with-ssl-termination)
     for passing the client certificate in the request header from the
     proxy over SSL tunneling.
 -   Support for [issuing access tokens per token
-    request](/using-wso2-identity-server/issuing-new-tokens-per-request) .
+    request](../../using-wso2-identity-server/issuing-new-tokens-per-request) .
 -   Support for [configuring a JWKS endpoint for a OAuth or OIDC based
-    service provider](/using-wso2-identity-server/private-key-jwt-client-authentication-for-oidc).
+    service provider](../../using-wso2-identity-server/private-key-jwt-client-authentication-for-oidc).
 -   Support for [configuring SAML metadata validity period for the
-    resident identity provider](/using-wso2-identity-server/adding-and-configuring-an-identity-provider/#exporting-saml2-metadata-of-the-resident-idP)
--   Includes [OAuth transaction logs](/using-wso2-identity-server/oauth-transaction-logs) for
+    resident identity provider](../../using-wso2-identity-server/adding-and-configuring-an-identity-provider/#exporting-saml2-metadata-of-the-resident-idP)
+-   Includes [OAuth transaction logs](../../using-wso2-identity-server/oauth-transaction-logs) for
     token generation and introspection.
--   Supports recaptcha for [password recovery](/using-wso2-identity-server/configuring-reCaptcha-for-password-recovery) and
-    [username recovery](/using-wso2-identity-server/configuring-reCaptcha-for-username-recovery).
+-   Supports recaptcha for [password recovery](../../using-wso2-identity-server/configuring-reCaptcha-for-password-recovery) and
+    [username recovery](../../using-wso2-identity-server/configuring-reCaptcha-for-username-recovery).
 
 ### What has changed in this release
 
@@ -37,7 +37,7 @@ changed in this release.The new implementation consists of event
 handlers that subscribe to authentication events.
 
 For more information, see [Migrating Data
-Publishers](/using-wso2-identity-server/migrating-data-publishers) .
+Publishers](../../using-wso2-identity-server/migrating-data-publishers) .
 
 ### Compatible versions
 

en/docs/getting-started/access-control-and-entitlement-management.md

@@ -11,12 +11,12 @@ entitlement management systems are governed by industry standard
 specifications, hence supporting security requirements for heterogeneous
 applications becomes easy.
 
-Click [here](/tutorials/access-control.md) for
+Click [here](../../tutorials/access-control.md) for
 more information on Access control.
 
 ### Types of access control
 
-![The various types of access control](/assets/img/concepts/types-of-access-control.png)
+![The various types of access control](../../assets/img/getting-started/types-of-access-control.png)
 
 The following table describes the various types of access control.
 
@@ -192,7 +192,7 @@ descriptive attributes about the user or any other missing attribute in
 the request. Policy Administration Point (PAP) is used to manage the PDP
 and PIP functionality.
 
-![XACML system architecture](/assets/img/concepts/xacml-system-architecture.png)
+![XACML system architecture](../../assets/img/getting-started/xacml-system-architecture.png)
 
 ------------------------------------------------------------------------
 
@@ -236,7 +236,7 @@ Point (PDP).
 
 The following diagram represents the component architecture of the PDP.
 
-![Component architecture of the policy decision point](/assets/img/concepts/xacml-engine-architecture.png)
+![Component architecture of the policy decision point](../../assets/img/getting-started/xacml-engine-architecture.png)
 
 The following provides a more detailed information on the various
 components available in the PDP architecture.
@@ -284,7 +284,7 @@ PDP is exposed via the Entitlement Admin Service with method name
 This module finds  from different policy stores to evaluate a
 XACML request. The following is a high-level diagram of how this works.
 
-![Carbon policy finder](/assets/img/concepts/carbon-policy-finder.png)
+![Carbon policy finder](../../assets/img/getting-started/carbon-policy-finder.png)
 
 Any number of policy finder modules can be plugged with the Carbon
 policy finder. You need to implement the CarbonPolicyFinderModule
@@ -421,7 +421,7 @@ This module helps to find the missing attribute for a given XACML
 request. The following is the high-level diagram for both the Carbon
 attribute and resource finders.
 
-![Carbon attribute finder](/assets/img/concepts/carbon-attribute-finder.png)
+![Carbon attribute finder](../../assets/img/getting-started/carbon-attribute-finder.png)
 
 Any number of PIP attribute finder modules can be plugged with the
 Carbon attribute finder. You need to implement the PIPAttributeFinder
@@ -1026,7 +1026,7 @@ above request:
 For a tutorial that demonstrate how WSO2 IS supports fine-grained
 authorization using XACML requests in JSON format, see [Fine-grained
 Authorization using XACML Requests in JSON
-Format](/tutorials/fine-grained-authorization-using-xacml-requests-in-json-format).
+Format](../../tutorials/fine-grained-authorization-using-xacml-requests-in-json-format).
 
 #### Administrative Delegation Profile