Self review

Author: maud-lv

articles/service-connector/concept-service-connector-internals.md

@@ -11,7 +11,9 @@ ms.date: 12/08/2022
 
 # Service Connector internals
 
-Service Connector is an Azure extension resource provider designed to provide a simple way to create and manage connections between Azure services. Service Connector:
+Service Connector is an Azure extension resource provider designed to provide a simple way to create and manage connections between Azure services. 
+
+Service Connector:
 
 - Enables you to connect services together with a single Azure CLI command or in a few steps in the Azure portal.
 - Supports an increasing number of databases, storage, real-time services, state, and secret stores that are used with your cloud native application.
@@ -20,21 +22,21 @@ Service Connector is an Azure extension resource provider designed to provide a
 
 ## Service connection overview
 
-Service connection is the key concept in the resource model of Service Connector. A service connection represents an abstraction of the link between two services.  Service connections have the following properties:
+The concept of *service connection* is a key concept in the resource model of Service Connector. A service connection represents an abstraction of the link between two services.  Service connections have the following properties:
 
 | Property            | Description                                                                                                                                                                                                                                  |
 |---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | Connection Name     | The unique name of the service connection.                                                                                                                                                                                                   |
-| Source Service Type | Source services are usually Azure compute services. Service Connector functionalities can be found in supported compute services by extending these Azure compute service providers.                                                         |
+| Source Service Type | Source services are usually Azure compute services. These are the services you can connect to target services. Source services include Azure App Service, Azure Container Apps and Azure Spring Apps.                                                       |
 | Target Service Type | Target services are backing services or dependency services that your compute services connect to. Service Connector supports various target service types including major databases, storage, real-time services, state, and secret stores. |
-| Client Type         | Client type refers to your compute runtime stack, development framework, or specific client library type, which accepts the specific format of the connection environment variables or properties.                                           |
+| Client Type         | Client type refers to your compute runtime stack, development framework, or specific type of client library that accepts the specific format of the connection environment variables or properties.                                           |
 | Authentication Type | The authentication type used for the service connection. It could be a secret/connection string, a managed identity, or a service principal.                                                                                                 |
 
-Source services and target services each support multiple service connections, which means that you can connect each resource to multiple resources.
+Source services and target services support multiple simultaneous service connections, which means that you can connect each resource to multiple resources.
 
-Service Connector manages connections in the properties of the source instance. It means that creating, getting, updating, and deleting connections os done directly by opening the source service instance in the Azure portal or by using the CLI commands of the source service.
+Service Connector manages connections in the properties of the source instance. Creating, getting, updating, and deleting connections is done directly by opening the source service instance in the Azure portal or by using the CLI commands of the source service.
 
-Connections can be made across subscriptions or tenants, means that source and target services can belong to different subscriptions or tenants. When you create a new service connection, the connection resource is created in the same region as your compute service instance by default.
+Connections can be made across subscriptions or tenants, meaning that source and target services can belong to different subscriptions or tenants. When you create a new service connection, the connection resource is created in the same region as your compute service instance by default.
 
 ## Service connection creation and update
 
@@ -76,8 +78,8 @@ Service Connector sets the connection configuration when creating a connection.
 - Spring Boot client: the Spring Boot library for each target service has its own naming convention. For example, MySQL connection settings would be `spring.datasource.url`, `spring.datasource.username`, `spring.datasource.password`. Kafka connection settings would be `spring.kafka.properties.bootstrap.servers`.
 
 - Other clients:
-  - When connecting to a target service, the key name of the first connection configuration uses the format `<Cloud>_<Type>_<Name>`. For example, `AZURE_STORAGEBLOB_RESOURCEENDPOINT`, `CONFLUENTCLOUD_KAFKA_BOOTSTRAPSERVER`.
-  - For the same type of target resource, the key name of the second connection configuration will use the format `<Cloud>_<Type>_<Connection Name>_<Name>`. For example, `AZURE_STORAGEBLOB_CONN2_RESOURCEENDPOINT`, `CONFLUENTCLOUD_KAFKA_CONN2_BOOTSTRAPSERVER`.
+  - The key name of the first connection configuration uses the format `<Cloud>_<Type>_<Name>`. For example, `AZURE_STORAGEBLOB_RESOURCEENDPOINT`, `CONFLUENTCLOUD_KAFKA_BOOTSTRAPSERVER`.
+  - For the same type of target resource, the key name of the second connection configuration uses the format `<Cloud>_<Type>_<Connection Name>_<Name>`. For example, `AZURE_STORAGEBLOB_CONN2_RESOURCEENDPOINT`, `CONFLUENTCLOUD_KAFKA_CONN2_BOOTSTRAPSERVER`.
 
 ## Service connection validation
 
@@ -90,4 +92,11 @@ The following items are checked while validating the connection:
 
 ## Connection deletion
 
-When a service connection is deleted, the connection information is also deleted..
+When a service connection is deleted, the connection information is also deleted.
+
+## Next steps
+
+Go to the concept article below to learn more about Service Connector.
+
+> [!div class="nextstepaction"]
+> [High availability](./concept-availability.md)