Fix small typos in the release announcement for 3.9

docs/community/3.9-announcement.md

@@ -168,7 +168,7 @@ Both `APIView.exclude_from_schema` and the `exclude_from_schema` argument to the
 
 For `APIView` you should instead set a `schema = None` attribute on the view class.
 
-For function based views the `@schema` decorator can be used to exclude the view from the schema, by using `@schema(None)`.
+For function-based views the `@schema` decorator can be used to exclude the view from the schema, by using `@schema(None)`.
 
 ---
 
@@ -179,13 +179,13 @@ There are a large number of minor fixes and improvements in this release. See th
 
 ## What's next
 
-We're planning to iteratively working towards OpenAPI becoming the standard schema
+We're planning to iteratively work towards OpenAPI becoming the standard schema
 representation. This will mean that the `coreapi` dependency will gradually become
 removed, and we'll instead generate the schema directly, rather than building
 a CoreAPI `Document` object.
 
 OpenAPI has clearly become the standard for specifying Web APIs, so there's not
-much value any more in our schema-agnostic document model. Making this change
+much value anymore in our schema-agnostic document model. Making this change
 will mean that we'll more easily be able to take advantage of the full set of
 OpenAPI functionality.
 
@@ -200,7 +200,7 @@ with the possibility that some of this work will eventually [feed back into
 Django](https://www.aeracode.org/2018/06/04/django-async-roadmap/).
 
 There will be further work on the [Uvicorn](https://www.uvicorn.org/)
-webserver, as well as lots of functionality planned for the [Starlette](https://www.starlette.io/)
+web server, as well as lots of functionality planned for the [Starlette](https://www.starlette.io/)
 web framework, which is building a foundational set of tooling for working with
 ASGI.