Updated docs

Signed-off-by: aryans1204 <arshar1204@gmail.com>

Author: aryans1204

docs/generate_deploy_info_docs.md

@@ -4,7 +4,7 @@ The `deploy_info.json` file is used to identify deployment information for servi
 
 ## Schema and Usage
 
-The `deploy_info.json` file in the `vSwarm_deploy_metadata.tar.gz`  is used to identify the relative file paths for the Knative YAML manifests for deploying vSwarm functions. It is generated using `workloads/container/generate_deploy_info.py` Python script, which outputs a JSON that embeds the yaml-location and pre-deployment commands for every vSwarm function. It also contains the path of YAML files needed as part of the pre-deployment commands to run certain vSwarm benchmarks, for example the `online-shop-database` which requires to be deployed before running `cartservice` benchmark.
+The `deploy_info.json` file in the `vSwarm_deploy_metadata.tar.gz`  is used to identify the relative file paths for the Knative YAML manifests for deploying vSwarm functions. It also contains the path of YAML files needed as part of the pre-deployment commands to run certain vSwarm benchmarks, for example the `online-shop-database` which requires to be deployed before running `cartservice` benchmark.
 
 The `deploy_info.json` has the following schema:
 ```console
@@ -17,7 +17,8 @@ The `deploy_info.json` has the following schema:
 }
 ```
 
-The `PredeploymentPath` is the path to the YAML file, which is applied via `kubectl apply -f`, before creating the service under `YamlLocation`. This pre-deployment step is required in some vSwarm benchmarks, like `cartservice` which depends on a separate service `online-shop-database` before it can be started.
+The `PredeploymentPath` is the path to the YAML file, which is applied via `kubectl apply -f`, before creating the service under `YamlLocation`. 
+
 ## Deployment File Generation
 
 While the `deploy_info.json` file ships with the `vSwarm_deploy_metadata.tar.gz`, In order to regenerate the `deploy_info.json` run from the root of this repository:

docs/loader.md

@@ -134,12 +134,12 @@ To run load generator use the following command:
 ```bash
 $ go run cmd/loader.go --config cmd/config_knative_trace.json
 ```
-To run load generator to use vSwarm functions based on `mapper_output.json` run the following:
+To run load generator with vSwarm functions based on `mapper_output.json` run the following:
 
 ```bash
 $ go run cmd/loader.go --config cmd/config_vswarm_trace.json
 ```
-The difference between instructing the loader to run vSwarm functions is by setting the `VSwarm` flag in the loader configuration to `true`. For information on how to configure the workload for load generator, please refer to `docs/configuration.md`.
+To direct the loader to execute vSwarm functions, set the `VSwarm` flag in the loader configuration `true`. For information on how to configure the workload for load generator, please refer to `docs/configuration.md`.
 
 Additionally, one can specify log verbosity argument as `--verbosity [info, debug, trace]`. The default value is `info`.