diff --git a/docs/docs/usage.md b/docs/docs/usage.md
index 770274a2..f20f88cc 100644
--- a/docs/docs/usage.md
+++ b/docs/docs/usage.md
@@ -55,7 +55,7 @@ Generates a temporary `Makefile` according to the MTA descriptor and runs the `m
| ----------- | ------- | ---------- | -----------------------------
| `-p (--platform)` | Optional | The name of the target deployment platform.
The supported deployment platforms are: - `cf` for SAP Cloud Platform, Cloud Foundry environment
- `neo` for the SAP Cloud Platform, Neo environment
- `xsa` for the SAP HANA XS advanced model
If this parameter is not provided, the project is built for the SAP Cloud Platform, Cloud Foundry environment | `mbt build -p=cf`
| `-s (--source)` | Optional | The path to the MTA project; the current path is set as the default. | `mbt build -p=cf -s=C:/TestProject`
-| `-t (--target)` | Optional | The folder for the generated `MTAR` file. If this parameter is not provided, the `MTAR` file is saved in the `mta_archives` subfolder of the current folder. If the parameter is provided, the `MTAR` file is saved in the root of the folder provided by the argument. | `mbt build -p=cf -t=C:/TestProject`
+| `-t (--target)` | Optional | The folder for the generated `MTAR` file. If this parameter is not provided, the `MTAR` file is saved in the `mta_archives` subfolder of the current folder. If the parameter is provided, the `MTAR` file is saved in the root of the folder provided by the argument. Relative paths are treated relatively to the path provided by the `-s (--source)` argument. | `mbt build -p=cf -t=C:/TestProject`
| `--mtar` | Optional | The file name of the generated archive file. If this parameter is omitted, the file name is created according to the following naming convention:
`_.mtar`
If the parameter is provided, but does not include an extension, the `.mtar` extension is added. | `mbt build -p=cf --mtar=TestProject.mtar`
| `-e (--extensions)` | Optional | The path or paths to multitarget application extension files (.mtaext). Several extension files separated by commas can be passed with a single flag, or each extension file can be specified with its own flag. |`mbt build -e=test1.mtaext,test2.mtaext`
or
`mbt build -e=test1.mtaext -e=test2.mtaext`
| `--strict` | Optional | The default value is `true`. If set to `true`, the duplicated fields and fields that are not defined in the `mta.yaml` schema are reported as errors. If set to `false`, they are reported as warnings. | `mbt build -p=cf --strict=true`
@@ -194,4 +194,4 @@ This command generates SBOMs for project modules and merges the SBOMs into one,
| Flag | Mandatory /
Optional | Description | Examples
| ----------- | ------- | ---------- | -----------------------------
| `-s (--source)` | Optional | The path to the MTA project; the current path is set as the default. | `mbt sbom-gen -s C:/TestProject -b sbom-file-gen/test.sbom.xml`
-| `-b (--sbom-file-path)` | Optional | The path of the SBOM file. The last part of the path is the file name.
- The sbom-file-path can be null. If the sbom-file-path is null, the default value is /.bom.xml.
- The sbom-file-path can be relative or abs; If the path is relative, it is the relative path to the project root.
- The sbom-file-path's last part is the file name.
- Only the XML file format is currently supported; So, if the file suffix is .xml, or if there's no file suffix, an XML format SBOM will be generated.
| `mbt sbom-gen --sbom-file-path sbom-gen/test.sbom.xml`
\ No newline at end of file
+| `-b (--sbom-file-path)` | Optional | The path of the SBOM file. The last part of the path is the file name.
- The sbom-file-path can be null. If the sbom-file-path is null, the default value is /.bom.xml.
- The sbom-file-path can be relative or abs; If the path is relative, it is the relative path to the project root.
- The sbom-file-path's last part is the file name.
- Only the XML file format is currently supported; So, if the file suffix is .xml, or if there's no file suffix, an XML format SBOM will be generated.
| `mbt sbom-gen --sbom-file-path sbom-gen/test.sbom.xml`