spelling I

.github/actions/spell-check/dictionary/microsoft.txt

@@ -1,3 +1,5 @@
+ACLs
+DACLs
 LKG
 mfcribbon
 microsoft
@@ -5,6 +7,7 @@ microsoftonline
 osgvsowi
 powerrename
 powershell
+SACLs
 tdbuildteamid
 vcruntime
 visualstudio

.github/actions/spell-check/expect/expect.txt

@@ -508,8 +508,8 @@ DECAUPSS
 DECAWM
 DECCKM
 DECCOLM
-decf
 DECEKBD
+decf
 DECKPAM
 DECKPM
 DECKPNM
@@ -1426,6 +1426,7 @@ Mul
 multiline
 munged
 mutex
+mutexes
 muxes
 myapplet
 mydir
@@ -1922,6 +1923,7 @@ RELBINPATH
 remoting
 renderengine
 rendersize
+reparent
 reparenting
 replatformed
 Replymessage
@@ -2101,8 +2103,8 @@ SHIFTJIS
 Shl
 shlguid
 shlobj
-shobjidl
 shlwapi
+shobjidl
 SHORTPATH
 SHOWCURSOR
 SHOWMAXIMIZED
@@ -2276,6 +2278,7 @@ terminalnuget
 TERMINALSCROLLING
 terminfo
 TEs
+tesroff
 testapp
 testcon
 testd
@@ -2390,8 +2393,8 @@ uap
 uapadmin
 UAX
 ubuntu
-ucd
 UCD
+ucd
 ucdxml
 uch
 UCHAR
@@ -2422,6 +2425,7 @@ unexpand
 Unfocus
 unfocuses
 unhighlighting
+unhosted
 unicode
 UNICODESTRING
 UNICODETEXT
@@ -2612,7 +2616,6 @@ wincontypes
 WINCORE
 windbg
 WINDEF
-winget
 WINDIR
 windll
 WINDOWALPHA
@@ -2641,6 +2644,7 @@ WINDOWTITLE
 winevent
 winfx
 wingdi
+winget
 WINIDE
 winioctl
 winmd

doc/specs/drafts/#1256 - Tab tearoff.md

@@ -31,7 +31,7 @@ There are several common pieces needed for both the tab tear-off scenario and th
 
 We need some sort of server/manager code that sits there waiting for connections from `wt.exe` processes and potentially `conhost.exe` processes such that it can broker a connection between the processes. It either needs to run in its own process or it needs to run in one of the existing `wt.exe`s that is chosen as the primary manager at the time. It should create communication channels and a global mutex at the time of creation.
 
-All other `wt.exe` processes starting after the primary should detect the existance of the server manager process and wait on the mutex handle. When the primary disappears, the OS scheduler should choose one of the others to wake up first on the mutex. It can take the lock and then set up the primary management channel. 
+All other `wt.exe` processes starting after the primary should detect the existence of the server manager process and wait on the mutex handle. When the primary disappears, the OS scheduler should choose one of the others to wake up first on the mutex. It can take the lock and then set up the primary management channel. 
 
 Alternatively, if the manager process is completely isolated and we expect all `wt.exe`s to have to remain connected at all times, we can make it such that when the connections are broken between the individual processes and the manager that they all shut down. I would prefer that it is resilient (the previous option) over this one, but browsers must have a good reason for preferring this way.
 
@@ -316,4 +316,4 @@ This might unlock some sort of isolation for extensions as well. Extensions of s
 - [Pipe Server documentation](https://docs.microsoft.com/en-us/windows/win32/ipc/multithreaded-pipe-server)
 - [OLE Drag and Drop](https://docs.microsoft.com/en-us/windows/win32/api/ole2/nf-ole2-registerdragdrop)
 - [OpenProcess](https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-openprocess)
-- [DuplicateHandle](https://docs.microsoft.com/en-us/windows/win32/api/handleapi/nf-handleapi-duplicatehandle)
+- [DuplicateHandle](https://docs.microsoft.com/en-us/windows/win32/api/handleapi/nf-handleapi-duplicatehandle)