TEMPORARY: change 3 files to trigger doc failures

docs/data-sources/search_deployment.md

@@ -27,16 +27,6 @@ resource "mongodbatlas_advanced_cluster" "example" {
   }
 }
 
-resource "mongodbatlas_search_deployment" "example" {
-  project_id   = mongodbatlas_project.example.id
-  cluster_name = mongodbatlas_advanced_cluster.example.name
-  specs = [
-    {
-      instance_size = "S20_HIGHCPU_NVME"
-      node_count    = 2
-    }
-  ]
-}
 
 data "mongodbatlas_search_deployment" "example" {
   project_id   = mongodbatlas_search_deployment.example.project_id

docs/resources/push_based_log_export.md

@@ -1,6 +1,6 @@
 # Resource: mongodbatlas_push_based_log_export
 
-`mongodbatlas_push_based_log_export` provides a resource for push-based log export feature. The resource lets you configure, enable & disable the project level settings for the push-based log export feature. Using this resource you 
+`mongodbatlas_push_based_log_export` provide a resource for push-based log export feature. The resource lets you configure, enable & disable the project level settings for the push-based log export feature. Using this resource you 
 can continually push logs from mongod, mongos, and audit logs to an Amazon S3 bucket. Atlas exports logs every 5 minutes.
 
 

docs/resources/search_deployment.md

@@ -4,8 +4,6 @@
 
 -> **NOTE:** For details on supported cloud providers and existing limitations you can visit the [Search Node Documentation](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution/#search-nodes-for-workload-isolation).
 
--> **NOTE:** Only a single search deployment resource can be defined for each cluster.
-
 ## Example Usages
 
 ```terraform