Add documentation for connection values and secrets to resource reference pages

.github/config/en-custom.txt

@@ -424,3 +424,6 @@ httpGet
 tcp
 BucketName
 Balancer
+authSource
+mongodb
+MYCONNECTION

docs/content/concepts/appmodel-concept/_index.md

@@ -75,13 +75,20 @@ The use cases for connections are flexible, and include features like:
 
 ### Injected values
 
-Declaring a connection between two resources also injects information in the form of environment variables based on the name of the connection and its kind. This is a form of *cloud-native service discovery* and makes it easy for you to decouple your application code from the environment where its deployed.
+When a connection between two resources is declared, Radius injects resource related information into environment variables that are then used to access the respective resource without having to hard code URIs, connection strings, secrets, etc. into your application code. This is a form of *cloud-native service discovery* and makes it easy for you to decouple your application code from the environment where its deployed.
 
-These environment variables follow a naming convention that makes their use predictable. The naming pattern includes the connection name, which is part of the consuming component. This way the code that needs to read the values gets to define how they are named.
+These environment variables follow a naming convention that makes their use predictable. The naming pattern is derived from the name given to the connection and its type, which determines what values are required. This way the code that needs to read the values gets to define how they are named. For example, adding a connection called `myconnection` that connects to a MongoDB resource would result in the following environment variables being injected:
+
+```bash
+# the connection string to the resource, e.g. 'mongodb://mongo:27017/mongo?authSource=admin'
+CONNECTION_MYCONNECTION_CONNECTIONSTRING
+# the type of connection, e.g. 'mongo-connector'
+CONNECTION_MYCONNECTION_DATABASE
+```
 
 Each kind of connection defines values that are useful for communication. These could be URIs, connection strings, access keys, or anything that application code needs to successfully communicate. Refer to each [resource's reference documentation]({{< ref resource-schema >}}) for more information.
 
-The values provided through connections are a convenience and are also available as properties and functions (for secrets) when authoring your IaC files. You can ignore the values generated by a connection if you prefer to be explicit, or if you already have a convention you like to follow.
+The values provided through connections are a convenience and are also available as properties and functions (for secrets) when authoring your IaC files. You can ignore the values generated by a connection if you prefer to be explicit, or if you already have another convention you would like to follow.
 
 Adding connections to the above IaC file, it becomes: