Merge pull request wso2#2851 from ruthryi/master-ru3

Update context at the Endpoints Documentation
RPIUdishan · Sep 29, 2021 · cb308b3 · cb308b3
2 parents aae8476 + 2cd8ec8
commit cb308b3
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/en/micro-integrator/docs/references/synapse-properties/endpoint-properties.md b/en/micro-integrator/docs/references/synapse-properties/endpoint-properties.md
@@ -583,7 +583,7 @@ The following is the configuration for the address endpoint. Note that you can a
         <enableAddressing [version="final|submission"] [separateListener="true|false"]/>?
 
         <timeout>
-                <duration>timeout duration in seconds</duration>
+                <duration>timeout duration in milliseconds</duration>
                 <responseAction>discard|fault|never</responseAction>
         </timeout>?
 
@@ -638,7 +638,7 @@ The `timeout` element contains the following parameters that are used to conside
                <li><b>Discard</b>:  If this is selected, the responses which arrive after the endpoint has timed out will be discarded.</li>
                <li><b>Fault</b>: If this is selected, a fault sequence is triggered when the endpoint is timed out.</li>
             </ul>
-            <b>Note</b>: You can specify a value that is 1 millisecond less than the time duration you specify for the endpoint time out for the <code>synapse.timeout_handler_interval</code> property in the <code>MI_Home/conf/ei.toml</code> file. This would minimise the number of late responses from the backend.
+            <b>Note</b>: You can specify a value that is 1 millisecond less than the time duration you specify for the endpoint time out for the <code>synapse.timeout_handler_interval</code> property in the <code>MI_Home/conf/deployment.toml</code> file. This would minimise the number of late responses from the backend.
             </ul>
          </td>
       </tr>

diff --git a/...e-cases/examples/file-processing/Accessing_Windows_Share_Using_VFS_Transport.md b/...e-cases/examples/file-processing/Accessing_Windows_Share_Using_VFS_Transport.md
@@ -1,7 +1,7 @@
 # Accessing a Windows Share using VFS
-This example demonstrates how the [VFS transport](../../setup/transport_configurations/configuring-transports/configuring-the-vfs-transport) in WSO2 Micro Integrator can be used to access a windows share.
+This example demonstrates how the [VFS transport](../../../../setup/transport_configurations/configuring-transports/#configuring-the-vfs-transport) in WSO2 Micro Integrator can be used to access a windows share.
 
-## Synapse configuration
+## Synapse configuration 
 
 Following are the integration artifacts (proxy service) that we can used to implement this scenario.