docs: fix

Author: iru

use-cases/README.md

@@ -20,10 +20,7 @@ and for AWS in [Cloudformation](https://github.com/sysdiglabs/aws-templates-secu
 
 |                   | `/examples/single-*`                                               | `/examples/organizational-*` |
 | --| -- | -- |
-| Deployment Type   | all Sysdig resources will be deployed within the selected account | Most Sysdig resources will 
-be deployed within the selected account (just one), but some features, require resources to be deployed on all of 
-the member-accounts (for Compliance and Image Scanning) . <br />One role is needed on the management account for 
-cloudtrail-s3 event access |
+| Deployment Type   | all Sysdig resources will be deployed within the selected account | Most Sysdig resources will be deployed within the selected account (just one), but some features, require resources to be deployed on all of the member-accounts (for Compliance and Image Scanning) . <br />One role is needed on the management account for cloudtrail-s3 event access |
 | Target          | will only analyse current account                                 |  handles all accounts (managed and member)|
 | Drawbacks         | cannot re-use another account Cloudtrail data (unless its deployed on the same account where the sns/s3 bucket is) | for scanning, a per-member-account access role is required |
 | Optional usage limitations | - |  For organizational example, optional resources must exist in the management account. For other setups check
@@ -52,12 +49,7 @@ Make use of optionals to allow the re-use of pre-existing resources, and avoid i
 
 |  Cloud |  Optionals | Related Input Vars | Other |
 | -- | --| -- | -- |
-| AWS  | Cloudtrail | single: [`cloudtrail_sns_arn`](https://github.
-com/sysdiglabs/terraform-aws-secure-for-cloud/tree/master/examples/single-account-ecs#input_cloudtrail_sns_arn)
-<br/>organizational: [`existing_cloudtrail_config`](https://github.
-com/sysdiglabs/terraform-aws-secure-for-cloud/tree/master/examples/organizational#input_existing_cloudtrail_config) 
-|  For organizational example, optional resources must exist in the management account. For other setups check 
-other alternative use-cases |
+| AWS  | Cloudtrail | single: [`cloudtrail_sns_arn`](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/tree/master/examples/single-account-ecs#input_cloudtrail_sns_arn)<br/>organizational: [`existing_cloudtrail_config`](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/tree/master/examples/organizational#input_existing_cloudtrail_config) |  For organizational example, optional resources must exist in the management account. For other setups check other alternative use-cases |
 | | ECS, VPC, Subnet | `ecs_cluster_name`, `ecs_vpc_id`, `ecs_vpc_subnets_private_ids` | if used, the three are mandatory  |
 | GCP | - | - | - |
 | Azure | ResourceGroup | `resource_group_name` | - |