description of Win32 as x86 to better scripting/programming for updaters or scripts
the Releasenames of Win32 , so in x86 or iX86bit is many in colloquial language "Win32"
bit in technical language is it x86 without the 64Bit extension, so should it name
not
Notepad2_XXX_Win32_v4.22.01r4056.zip
it should be named
Notepad2_XXX_x86_v4.22.01r4056.zip
to have it more easy for a downloader or system called architecture
like them of microsoft selective file format where can call for x64=x86_64
or only x86 .. ther with it's possible in programmed tools for more easy selective to download the file
as example :
Notepad2_i18n_x86_v4.22.01r4056.zip
or
Notepad2_i18n_x64_v4.22.01r4056.zip
in batch-scripting of WinNT is this as example this :
::>>>==Check the Architecture=================================================
:arch
set parch=%PROCESSOR_ARCHITECTURE%
set xparch=%PROCESSOR_ARCHITEW6432%
If "%xparch%"=="AMD64" ( set arch=x64
) else ( If "%parch%"=="x86" ( set arch=x86
goto :eof
) else (
If "%parch%"=="AMD64" ( set arch=x64
) else (
set arch=
goto :eof )
)
)
goto :eof
::<<<==Check the Architecture=================================================
this makes the variable at WinNT as "arch" in either x86 or x64 and therwith it's possible to set a selecting achitecture, at the update/service-files from MS or other, therewith it's important to have a "ISO/standard" naming for to have a possibility to selecting.. and the "Win32" is it not , but x86 it is.
best regards Blacky
I think the simplest change is update release page, change the word "Architecture" to "Platform".

have it nothing to do with arm, it's the WinNT, "_win32_" to "_x86_" renamed if it's possible
for the next releases, because then it's possible to select the architecture more easy out of a batchfile
or an other program like in python, vb or other :)
i use the batchfile like this :
https://www.blackysgate.de/files/folder-root/batch-files/
https://www.blackysgate.de/files/folder-root/batch-files/setup-update-batch-1.72.bat.cmd
best Blacky
hmm...
I think it's not worth to make the requested change, the Win32 build works everywhere with a Win32 compatible environment (e.g. Windows, Wine and ReactOS) on x86, x86_64, arm, arm64, RISC-V, etc. As Win32 has been used sine the beginning (2017), change it may break someone else's automation script/tool. There are other popular projects also use Win32 as suffix, e.g. LLVM (see https://github.com/llvm/llvm-project/releases/tag/llvmorg-15.0.6).