Update README.ENV.md

readme/README.ENV.md

@@ -8,9 +8,8 @@ To enable the Redis Cache of Azure in eShop it is necessary to have previously c
 For example:
 >ESHOP_AZURE_REDIS_BASKET_DB=yourredisservice.redis.cache.windows.net:6379,password=yourredisservicepassword,ssl=False,abortConnect=False
 
-With the steps explained in the next section, you will be able to run the application with Azure Service Bus instead of the container of RabbitMQ service.
-
 # Azure Service Bus service
+With the steps explained in this section, you will be able to run the application with Azure Service Bus instead of the container of RabbitMQ service.
 To enable the service bus of Azure in eShop solution it is necessary having created previously the service bus service through ARM file or manually through Azure portal. You can use the [ARM files](deploy/az/servicebus/readme.md) already created in eShop. Finally, it is necessary to get the Shared access policy named "Root" (if you generated the service through ARM file) from eshop_event_bus topic. This policy must be declared on .env file located in the solution root folder with `ESHOP_AZURE_SERVICE_BUS` name.
 
 For example:
@@ -18,9 +17,8 @@ For example:
 
 Once the service bus service is created, it is necessary to set to true the "AzureServiceBusEnabled" environment variable from `settings.json` file on Catalog.API, Ordering.API, Basket.API, Payment.API, GracePeriodManager, Marketing.API and Locations.API.
 
-With the steps explained in the next section, you will be able to run the application with Azure Storage Account instead of the local container storage.
-
 # Azure Storage Account service
+With the steps explained in this section, you will be able to run the application with Azure Storage Account instead of the local file folder storage.
 To enable Azure storage of Azure in eShopOnAzure solution it is necessary having created previously the storage service through ARM file or manually through Azure portal. You can use the ARM files find under **deploy/az/storage** folder already created in eShop. Once the storage account is created, it is very important to create a new container(blob kind) and upload the solution catalog pics files before to continue.Later, it is necessary to set to true the "AzureStorageEnabled" environment variable from `settings.json` in Catalog.API and Marketing.API.Finally, it is necessary to get the container endpoint url from information service in the Azure portal, This url must be declared on .env file located in the solution root folder with `ESHOP_AZURE_STORAGE_CATALOG` for the Catalog.API content and `ESHOP_AZURE_STORAGE_MARKETING` for the Marketing.API content.
 
 Do not forget to put a slash character '/' in the end of the url.
@@ -39,9 +37,8 @@ For example:
 >ESHOP_AZURE_STORAGE_MARKETING_NAME=storageaccountname
 >ESHOP_AZURE_STORAGE_MARKETING_KEY=storageaccountkey
 
-With the steps explained in the next section, you will be able to run the application with Azure SQL Database instead of local storage.
-
 # Azure SQL Database
+With the steps explained in this section, you will be able to run the application with Azure SQL Database instead of a local SQL Server container.
 To enable Azure SQL Database in eShop is required to have a Azure SQL with the databases for Ordering.API, Identity.API, Catalaog.API and Marketing.API. You can use the [ARM files](deploy/az/sql/readme.md) already created in this project or do it manually. Once the databases are created, it is necessary to get the connection string for each service and set the corresponding variable in the .env file.
 
 For example:
@@ -50,9 +47,8 @@ For example:
 >ESHOP_AZURE_ORDERING_DB=orderingazureconnectionstring
 >ESHOP_AZURE_MARKETING_DB=marketingazureconnectionstring
 
-With the steps explained in the next section, you will be able to run the application with Azure Cosmos DB Database instead of local storage.
-
 # Azure Cosmos DB
+With the steps explained in this section, you will be able to run the application with Azure Cosmos DB Database instead of a local MongoDB container.
 To enable Azure Cosmos DB in eShop is required to have the connection string. If you do not have an Azure Cosmos DB created you can use the ARM files under **deploy/az/cosmos** folder available in eShop or do it manually. Once the connection string is availabe it is necessary to add it in the .env file in the `ESHOP_AZURE_COSMOSDB`variable.
 
 For example:
@@ -64,4 +60,4 @@ To enable the Azure Functions in eShop you can add the URI where the functions h
 For example:
  >ESHOP_AZUREFUNC_CAMPAIGN_DETAILS_URI=https://marketing-functions.azurewebsites.net/api/MarketingDetailsHttpTrigger?code=AzureFunctioncode
  
-See Azure Functions deployment Files and Readme for more details [ARM files](deploy/az/azurefunctions/readme.md)
+See Azure Functions deployment Files and Readme for more details [ARM files](deploy/az/azurefunctions/readme.md)