Apply suggestions from code review

Co-authored-by: Rainer Sigwald <raines@microsoft.com>

DEVGUIDE.md

@@ -46,7 +46,7 @@ To use your locally built packages:
 
 ## Using the package when implicit SDK support is enabled
 
-If you are on SDK 7.0.2xx or greater, are a Web SDK project, and have `EnableSdkContainerSupport` set to `true` in your project file, you will need to use another mechanism to reference the generated package. You can do one of the following actions:
+If you are on SDK 7.0.200 or greater, are a Web SDK project, and have `EnableSdkContainerSupport` set to `true` in your project file, you will need to use another mechanism to reference the generated package. You can do one of the following actions:
 
 * Set `EnableSdkContainerSupport` to `false` in your project file and use a normal PackageReference as described above,
 * Keep `EnableSdkContainerSupport` set to `true` and set the `SdkContainerSupportPackageVersion` property to the version you built above,

docs/ContainerCustomization.md

@@ -34,7 +34,7 @@ By default, if your project has a RuntimeIdentifier set, that value will be used
 ```
 
 > **Note**
-> If you'd like to publish to a musl-based OS like alpine (as opposed to a libc-based OS), you will need to specify the base image _exactly_, instead of relying on
+> If you'd like to publish to a musl-based OS like alpine (as opposed to a libc-based OS), you will need to specify the base image _including architecture_, instead of relying on
 > any of the inference described above. For example, a `net7.0`-targeting application that wanted to run on alpine with the x64 architecture would use the `7.0-alpine-amd64` tag of the `mcr.microsoft.com/dotnet/runtime` image (or another base image as appropriate for your project type):
 >
 > ```xml