diff --git a/internal/resolution/pm/gomod/README.md b/internal/resolution/pm/gomod/README.md
index 4c4c9962..7cba57cb 100644
--- a/internal/resolution/pm/gomod/README.md
+++ b/internal/resolution/pm/gomod/README.md
@@ -3,6 +3,6 @@
 The way resolution of go lock files works is as follows:
 
 1. Run `go mod graph` in order to create dependency graph
-2. Run `go list -mod=readonly -e -m all` to get the contents of the requirements.txt file
+2. Run `go list -mod=readonly -e -m all` to get the list of packages
 
 The results of the commands above are then combined to form the finished lock file.
diff --git a/internal/resolution/pm/nuget/README.md b/internal/resolution/pm/nuget/README.md
index 66eff764..9c247397 100644
--- a/internal/resolution/pm/nuget/README.md
+++ b/internal/resolution/pm/nuget/README.md
@@ -18,4 +18,4 @@ With this done we can move on to the next section
 ### .csproj
 
 1. Run `dotnet restore <file> --use-lock-file --lock-file-path <lock_file>` in order to restore the dependencies and tools of a project (lock file name can be different depend on which manifest file is being resolved)
-2. Cleanup temporary csproj file after lock file is created (for `packages.comfig` case)
+2. Cleanup temporary csproj file after lock file is created (for `packages.config` case)