Switch ordering of configuration examples in cost report and optimization tables

Author: cbruno10

docs/tables/aws_cost_and_usage_focus/index.md

@@ -129,37 +129,37 @@ order by
 
 ## Example Configurations
 
-### Collect for a specific export
+### Collect reports from an S3 bucket
 
-For a specific export (`my-focus-export` in this example), collect Cost and Usage FOCUS reports.
+Collect Cost and Usage FOCUS reports stored in an S3 bucket that use the [default log file name format](https://docs.aws.amazon.com/cur/latest/userguide/dataexports-export-delivery.html#export-summary).
+
+**Note**: We only recommend using the default log file name format if the bucket and prefix combination contains Cost and Usage FOCUS reports. If other reports, like the Cost and Usage Report 2.0, are stored in the same S3 bucket with the same prefix, Tailpipe will attempt to collect from these too, resulting in errors.
 
 ```hcl
 connection "aws" "billing_account" {
   profile = "my-billing-account"
 }
 
-partition "aws_cost_and_usage_focus" "specific_cur_focus" {
-  source "aws_s3_bucket"  {
-    connection  = connection.aws.billing_account
-    bucket      = "aws-cur-org-bucket"
-    prefix      = "my/prefix/"
-    file_layout = "my-focus-export/data/%{DATA:partition}/(?:%{TIMESTAMP_ISO8601:timestamp}-%{UUID:execution_id}/)?%{DATA:filename}.csv.gz"
+partition "aws_cost_and_usage_focus" "my_cur_focus" {
+  source "aws_s3_bucket" {
+    connection = connection.aws.billing_account
+    bucket     = "aws-cur-billing-bucket"
+    prefix     = "my/prefix/"
   }
 }
 ```
 
-### Collect reports from an S3 bucket
-
-Collect Cost and Usage FOCUS reports stored in an S3 bucket that use the [default log file name format](https://docs.aws.amazon.com/cur/latest/userguide/dataexports-export-delivery.html#export-summary).
+### Collect for a specific export
 
-**Note**: We only recommend using the default log file name format if the bucket and prefix combination contains Cost and Usage FOCUS reports. If other reports, like the Cost and Usage Report 2.0, are stored in the same S3 bucket with the same prefix, Tailpipe will attempt to collect from these too, resulting in errors.
+For a specific export (`my-focus-export` in this example), collect Cost and Usage FOCUS reports.
 
 ```hcl
-partition "aws_cost_and_usage_focus" "my_cur_focus" {
-  source "aws_s3_bucket" {
-    connection = connection.aws.billing_account
-    bucket     = "aws-cur-billing-bucket"
-    prefix     = "my/prefix/"
+partition "aws_cost_and_usage_focus" "specific_cur_focus" {
+  source "aws_s3_bucket"  {
+    connection  = connection.aws.billing_account
+    bucket      = "aws-cur-org-bucket"
+    prefix      = "my/prefix/"
+    file_layout = "my-focus-export/data/%{DATA:partition}/(?:%{TIMESTAMP_ISO8601:timestamp}-%{UUID:execution_id}/)?%{DATA:filename}.csv.gz"
   }
 }
 ```

docs/tables/aws_cost_and_usage_report/index.md

@@ -133,15 +133,31 @@ order by
 
 ## Example Configurations
 
-### Collect for a specific CUR 2.0 export
+### Collect reports from an S3 bucket
 
-For a specific export (`my-cur-2-0-export` in this example), collect Cost and Usage 2.0 reports.
+Collect Cost and Usage reports stored in an S3 bucket that use the [default log file name format](https://docs.aws.amazon.com/cur/latest/userguide/dataexports-export-delivery.html#export-summary).
+
+**Note**: We only recommend using the default log file name format if the bucket and prefix combination contains Cost and Usage reports. If other reports, like the Cost and Usage FOCUS report, are stored in the same S3 bucket with the same prefix, Tailpipe will attempt to collect from these too, resulting in errors.
 
 ```hcl
 connection "aws" "billing_account" {
   profile = "my-billing-account"
 }
 
+partition "aws_cost_and_usage_report" "my_cur" {
+  source "aws_s3_bucket" {
+    connection = connection.aws.billing_account
+    bucket     = "aws-cur-billing-bucket"
+    prefix     = "my/prefix/"
+  }
+}
+```
+
+### Collect for a specific CUR 2.0 export
+
+For a specific export (`my-cur-2-0-export` in this example), collect Cost and Usage 2.0 reports.
+
+```hcl
 partition "aws_cost_and_usage_report" "specific_cur_2_0" {
   source "aws_s3_bucket"  {
     connection  = connection.aws.billing_account
@@ -167,22 +183,6 @@ partition "aws_cost_and_usage_report" "specific_cur_legacy" {
 }
 ```
 
-### Collect reports from an S3 bucket
-
-Collect Cost and Usage reports stored in an S3 bucket that use the [default log file name format](https://docs.aws.amazon.com/cur/latest/userguide/dataexports-export-delivery.html#export-summary).
-
-**Note**: We only recommend using the default log file name format if the bucket and prefix combination contains Cost and Usage reports. If other reports, like the Cost and Usage FOCUS report, are stored in the same S3 bucket with the same prefix, Tailpipe will attempt to collect from these too, resulting in errors.
-
-```hcl
-partition "aws_cost_and_usage_report" "my_cur" {
-  source "aws_s3_bucket" {
-    connection = connection.aws.billing_account
-    bucket     = "aws-cur-billing-bucket"
-    prefix     = "my/prefix/"
-  }
-}
-```
-
 ### Collect reports from local files
 
 You can also reports from local files.

docs/tables/aws_cost_optimization_recommendation/index.md

@@ -132,25 +132,6 @@ order by
 
 ## Example Configurations
 
-### Collect for a specific export
-
-For a specific export (`my-recommendations-export` in this example), collect cost optimization recommendations.
-
-```hcl
-connection "aws" "billing_account" {
-  profile = "my-billing-account"
-}
-
-partition "aws_cost_optimization_recommendation" "specific_recommendations" {
-  source "aws_s3_bucket" {
-    connection  = connection.aws.billing_account
-    bucket      = "aws-cost-optimization-recommendations-bucket"
-    prefix      = "my/prefix/"
-    file_layout = "my-recommendations-export/data/%{DATA:partition}/(?:%{TIMESTAMP_ISO8601:timestamp}-%{UUID:execution_id}/)?%{DATA:filename}.csv.gz"
-  }
-}
-```
-
 ### Collect recommendations from an S3 bucket
 
 Collect cost optimization recommendations stored in an S3 bucket that use the [default log file name format](https://docs.aws.amazon.com/cur/latest/userguide/dataexports-export-delivery.html#export-summary).
@@ -171,6 +152,21 @@ partition "aws_cost_optimization_recommendation" "my_recommendations" {
 }
 ```
 
+### Collect for a specific export
+
+For a specific export (`my-recommendations-export` in this example), collect cost optimization recommendations.
+
+```hcl
+partition "aws_cost_optimization_recommendation" "specific_recommendations" {
+  source "aws_s3_bucket" {
+    connection  = connection.aws.billing_account
+    bucket      = "aws-cost-optimization-recommendations-bucket"
+    prefix      = "my/prefix/"
+    file_layout = "my-recommendations-export/data/%{DATA:partition}/(?:%{TIMESTAMP_ISO8601:timestamp}-%{UUID:execution_id}/)?%{DATA:filename}.csv.gz"
+  }
+}
+```
+
 ### Collect recommendations from local files
 
 You can also collect AWS cost optimization recommendations from local files.