Clarify relationship between project and directory names (dotnet#9830)

drewnoakes · BillWagner · commit 904a8f78d37a · 2019-02-22T15:38:19.000-05:00
The project name does not have to match the directory name, although they are usually created in this way. I feel this change makes it clearer where the default `&lt;AssemblyName&gt;` and `&lt;PackageId&gt;` properties come from.
diff --git a/docs/core/tools/project-json-to-csproj.md b/docs/core/tools/project-json-to-csproj.md
@@ -33,7 +33,7 @@ The new format, \*.csproj, is an XML-based format. The following example shows t
 }
 ```
 
-No longer supported. In csproj, this is determined by the project filename, which is defined by the directory name. For example, `MyProjectName.csproj`.
+No longer supported. In csproj, this is determined by the project filename, which usually matches the directory name. For example, `MyProjectName.csproj`.
 
 By default, the project filename also specifies the value of the `<AssemblyName>` and `<PackageId>` properties.
 

Original file line number	Diff line number	Diff line change
`@@ -33,7 +33,7 @@ The new format, \*.csproj, is an XML-based format. The following example shows t`
`33`	`33`	`}`
`34`	`34`	```
`35`	`35`
`36`		-No longer supported. In csproj, this is determined by the project filename, which is defined by the directory name. For example, `MyProjectName.csproj`.
	`36`	+No longer supported. In csproj, this is determined by the project filename, which usually matches the directory name. For example, `MyProjectName.csproj`.
`37`	`37`
`38`	`38`	By default, the project filename also specifies the value of the `<AssemblyName>` and `<PackageId>` properties.
`39`	`39`