From 9169d917a11534c3c6cd44ca3469f332283bf7ae Mon Sep 17 00:00:00 2001 From: Tom Dykstra Date: Wed, 25 Dec 2024 09:17:13 -0800 Subject: [PATCH] get rid of curly apostrophes --- aspnetcore/test/http-files.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/aspnetcore/test/http-files.md b/aspnetcore/test/http-files.md index 044b1efaf5..c63bb97710 100644 --- a/aspnetcore/test/http-files.md +++ b/aspnetcore/test/http-files.md @@ -192,7 +192,7 @@ In the preceding example, the `$shared` environment defines the `HostAddress` va ## User-specific environment files -A user-specific value is any value that an individual developer wants to test with but doesn’t want to share with the team. Since the `http-client.env.json` file is checked in to source control by default, it wouldn’t be appropriate to add user-specific values to this file. Instead, put them in a file named `http-client.env.json.user` located in the same folder as the `http-client.env.json` file. Files that end with `.user` should be excluded from source control by default when using Visual Studio source control features. +A user-specific value is any value that an individual developer wants to test with but doesn't want to share with the team. Since the `http-client.env.json` file is checked in to source control by default, it wouldn't be appropriate to add user-specific values to this file. Instead, put them in a file named `http-client.env.json.user` located in the same folder as the `http-client.env.json` file. Files that end with `.user` should be excluded from source control by default when using Visual Studio source control features. When the `http-client.env.json` file is loaded, Visual Studio looks for a sibling `http-client.env.json.user` file. If a variable is defined in an environment in both the `http-client.env.json` file and the `http-client.env.json.user` file, the value in the `http-client.env.json.user` file wins. @@ -354,7 +354,7 @@ GET {{HostAddress}}{{Path}} X-UserName: {{$processEnv USERNAME}} ``` -If you try to use `$processEnv` to access an environment variable that doesn’t exist, the `.http` file editor displays an error message. +If you try to use `$processEnv` to access an environment variable that doesn't exist, the `.http` file editor displays an error message. ## `.env` files