man: updated mkwin and wt manuals

README.md

@@ -1,8 +1,8 @@
 
 # Winure: WSL inurement tools
 
-These are tools I use to use Windows primarily through WSL. A lot of them
-assume you have PowerShell somewhere in your `PATH` as "`pwsh`".
+These are tools I use to use Windows primarily through WSL. Many are
+cross-dependent.
 
 ## `dos-var`
 

man/mkwin.1

@@ -56,11 +56,11 @@ Windows Explorer does not accept paths with spaces when executed from WSL. To ge
 .Pp
 Windows Terminal's executable moves when updated. To generate a script to launch Windows Terminal:
 .Pp
-.Dl $ mkwin --empty --find='/mnt/c/Program Files/WindowsApps/Microsoft.WindowsTerminal*' WindowsTerminal.exe > terminal.sh
+.Dl $ mkwin --empty --find='/mnt/c/Program Files/WindowsApps/Microsoft.WindowsTerminal*' WindowsTerminal.exe > wt.sh
 .Pp
-PowerShell doesn't inherit environment variables from WSL. To generate a script to call PowerShell with shared variables:
+PowerShell has two versions (Core is user-installed) and doesn't inherit environment variables from WSL. To generate a script to call PowerShell Core with a fallback to Windows PowerShell and shared environment variables:
 .Pp
-.Dl $ mkwin -E '/mnt/c/Program Files/PowerShell/7/pwsh.exe'
+.Dl $ mkwin -E '/mnt/c/Program Files/PowerShell/7/pwsh.exe' --or '/mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe'
 .Pp
 .Sh SEE ALSO
 .Xr env-share 1 ,

man/wt.1

@@ -3,7 +3,7 @@
 .Os MICROSOFT WINDOWS
 .Sh NAME
 .Nm wt
-launch Windows Terminal from WSL.
+.Nd Windows Terminal
 .Sh SYNOPSIS
 .Nm
 .Op Fl hv