docs(importing-resources): fix wording (#1607)

aiven · Feb 21, 2024 · 562ce34 · 562ce34
1 parent a667623
commit 562ce34
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/docs/guides/importing-resources.md b/docs/guides/importing-resources.md
@@ -5,7 +5,7 @@ page_title: "Importing existing Aiven infrastructure"
 # Importing existing Aiven infrastructure
 If you have already manually created an Aiven environment, it is possible to import all resources and start managing them with Terraform.
 
-The ID format for each resource but typically it is `<project_name>/<resource_name>` for resources that are directly under project level and `<project_name>/<service_name>/<resource_name>` for resources that belong to specific service.
+The ID format typically is `<project_name>/<resource_name>` for resources that are directly under project level and `<project_name>/<service_name>/<resource_name>` for resources that belong to specific service.
 
 As example, to import a database called `mydb` belonging to the service `myservice` in the project `myproject`, you can run:
 ```bash 
@@ -15,4 +15,4 @@ $ terraform import aiven_database.mydb myproject/myservice/mydb
 In some cases the internal identifiers are not shown in the Aiven web console. In such cases the easiest way to obtain identifiers is typically to check network requests and responses with your browser's debugging tools, as the raw responses do contain the IDs.
 
 ## Using data sources
-Alternatively you can define already existing, or externally created and managed, resources as [data sources](../data-sources).
+Alternatively you can define already existing, or externally created and managed, resources as [data sources](../data-sources).
diff --git a/templates/guides/importing-resources.md b/templates/guides/importing-resources.md
@@ -5,7 +5,7 @@ page_title: "Importing existing Aiven infrastructure"
 # Importing existing Aiven infrastructure
 If you have already manually created an Aiven environment, it is possible to import all resources and start managing them with Terraform.
 
-The ID format for each resource but typically it is `<project_name>/<resource_name>` for resources that are directly under project level and `<project_name>/<service_name>/<resource_name>` for resources that belong to specific service.
+The ID format typically is `<project_name>/<resource_name>` for resources that are directly under project level and `<project_name>/<service_name>/<resource_name>` for resources that belong to specific service.
 
 As example, to import a database called `mydb` belonging to the service `myservice` in the project `myproject`, you can run:
 ```bash 
@@ -15,4 +15,4 @@ $ terraform import aiven_database.mydb myproject/myservice/mydb
 In some cases the internal identifiers are not shown in the Aiven web console. In such cases the easiest way to obtain identifiers is typically to check network requests and responses with your browser's debugging tools, as the raw responses do contain the IDs.
 
 ## Using data sources
-Alternatively you can define already existing, or externally created and managed, resources as [data sources](../data-sources).
+Alternatively you can define already existing, or externally created and managed, resources as [data sources](../data-sources).