Improve clarity in Azure Functions documentation

AzureMentor · web-flow · commit a793c82d3968 · 2025-02-23T21:52:41.000-05:00
In the "Local project files" section, let's refer to the specific "local.settings.json" file by name instead of the generic term "local settings file" for greater clarity.
diff --git a/articles/azure-functions/functions-develop-local.md b/articles/azure-functions/functions-develop-local.md
@@ -46,7 +46,7 @@ The local.settings.json file stores app settings and settings used by local deve
 > [!IMPORTANT]  
 > Because the local.settings.json may contain secrets, such as connection strings, you should never store it in a remote repository. Tools that support Functions provide ways to synchronize settings in the local.settings.json file with the [app settings](functions-how-to-use-azure-function-app-settings.md#settings) in the function app to which your project is deployed.
 
-The local settings file has this structure:
+The **local.settings.json** file has this structure:
 
 ```json
 {

Original file line number	Diff line number	Diff line change
`@@ -46,7 +46,7 @@ The local.settings.json file stores app settings and settings used by local deve`
`46`	`46`	`> [!IMPORTANT]`
`47`	`47`	`> Because the local.settings.json may contain secrets, such as connection strings, you should never store it in a remote repository. Tools that support Functions provide ways to synchronize settings in the local.settings.json file with the [app settings](functions-how-to-use-azure-function-app-settings.md#settings) in the function app to which your project is deployed.`
`48`	`48`
`49`		`-The local settings file has this structure:`
	`49`	`+The local.settings.json file has this structure:`
`50`	`50`
`51`	`51`	```json
`52`	`52`	`{`