updated flow charts by adding START and END steps (#128)

Signed-off-by: neelanjan00 <neelanjan@chaosnative.com>

website/versioned_docs/version-2.0.0/architecture/chaos-observability-flow-analytics.md

@@ -19,4 +19,4 @@ In Litmus, workflow run statistics and information are generated post the chaos
 4. The request for the workflow statistics and information is received by the Backend Server.
 5. Backend Server queries the Database for the details of past Workflow Runs.
 6. Aggregated workflow statistics based on the ChaosResult verdict and probe success percentage are fetched from the Database by Backend Server. 
-7. Workflow statistics and information are forwarded to ChaosCenter by Backend Server.
+7. Workflow statistics and information are forwarded to ChaosCenter by Backend Server.

website/versioned_docs/version-2.0.0/architecture/chaos-observability-flow-summarisation.md

@@ -18,4 +18,4 @@ In Litmus, summarisation is performed using the ChaosResult CR. It stores all th
 3. When a user requests for the ChaosResult for a particular Chaos Experiment using the ChaosCenter, the request is received by the Backend Server.
 4. Backend Server queries the Database for the particular ChaosResult for the input Chaos Experiment.
 5. The ChaosResult is fetched from the Database by the Backend Server. 
-6. ChaosResult is forwarded to the ChaosCenter.
+6. ChaosResult is forwarded to the ChaosCenter.