Feedback.

Author: floitsch

docs/language/package/pkgtutorial.mdx

@@ -146,7 +146,7 @@ developers that it's even more the case.
 Packages should have a license. We recommend a
 [permissive free software license](https://en.wikipedia.org/wiki/Permissive_software_license),
 such as MIT, or BSD for packages that are published publicly. This is not a requirement,
-but more restrictive licenses are often avoided and would lead to fewer users of a package.
+but more restrictive licenses are often avoided and could lead to fewer users of a package.
 
 For our tutorial we use the MIT license. Our LICENSE file thus has the following text in it:
 
@@ -443,7 +443,7 @@ The easiest way to publish a package is to upload the sources to GitHub and to u
 [publish action](https://github.com/toitlang/action-publish).
 
 At each release it automatically takes the version number and informs the Toit package registry about the new
-release. Just make sure that the version is of the form `v1.0.0` (or similar). Version numbers follow
+release. Just make sure that the version is of the form `v1.0.0`. Version numbers follow
 [semantic versioning](https://semver.org) and tags must be valid semver versions with a prefixed 'v'.
 
 <Tabs>