Update index.mdx

product_docs/docs/pgd/4/deployments/tpaexec/index.mdx

@@ -20,13 +20,18 @@ TPAexec packages are only available to EDB customers with an active BDR subscrip
 ### Configuration
 The `tpaexec configure` command generates a simple YAML configuration file to describe a cluster, based on the options you select. The configuration is ready for immediate use, and you can modify it to better suit your needs. Editing the configuration file is the usual way to make any configuration changes to your cluster, both before and after it's created.
 
-The configuration options include: 
+The syntax is:
+
+```
+tpaexec configure <cluster_dir> --architecture <architecture_name> --layout <layout> --bdr-version <bdr_version> --<postgresql_flavour> --2Q-repositories <repositories_to_be_used> --extra-packages edb-livecompare edb-lasso --platform <platform>
+```
+
+The primary configuration options include: 
 
 | Flags                        | Description |
 | ---------------------------- | ----------- |
 | --architecture BDR-Always-ON | Required. Set to 'BDR-Always-ON' for EDB Postgres Distributed deployments |
 | --layout layoutname          | Required. Specify one of the four supported architectures: bronze, silver, gold, and platinum. See [Choosing your architecture][/pgd/4/architectures] for more information. |
-
 | --harp-consensus-protocol    | Required. `bdr` is recommended if your layout is bronze or silver. `etcd` is recommended if your layout is gold or platinum. See [Choosing your DCS]/pgd/4/dcs] for more information. |
 | --bdr-node-group groupname   | Optional. Set the name of the BDR node group. The default is `bdrgroup`. |
 | --bdr-database dbname        | Optional. Set the name of the database with BDR enabled. The default is `bdrdb`. |