Update Project-scope-and-goals.md (#509)

### Motivation

One of the examples no longer applies, we now do support customizing the
access modifier.

### Modifications

Updated the docs.

### Result

More accurate docs.

### Test Plan

N/A

---------

Co-authored-by: Si Beaumont <[email protected]>

Author: czechboy0

Sources/swift-openapi-generator/Documentation.docc/Articles/Project-scope-and-goals.md

@@ -38,9 +38,11 @@ Another example is the generation of empty structs within the input or output ty
 
 Some generators offer lots of options that affect the code generation process. In order to keep the project streamlined and maintainable, Swift OpenAPI Generator offers very few options.
 
-One concrete example of this is that users cannot configure the access modifier for generated code, nor does the generated code make any provision for namespace collisions in the target into which it is generated.
+One concrete example of this is that users cannot configure the names of generated types, such as `Client` and `APIProtocol`, and there is no attempt to prevent namespace collisions in the target into which it is generated.
 
-Instead, users are advised to generate code into its own target, and use Swift's module system to separate the generated code from code that uses it.
+Instead, users are advised to generate code into a dedicated target, and use Swift's module system to separate the generated code from code that depends on it.
+
+Another example is the lack of ability to customize how Swift names are computed from strings provided in the OpenAPI document.
 
 You can read more about this in <doc:API-stability-of-generated-code>.