Live F37 (KDE) wrong install

I wanted to fresh install F37, by downloading my favourite spin KDE Plasma Desktop via Fedora Media Writer on a USB pen to run live.
Everything went smoothly, I chose the traditional (not LVM) partitioning way on a superfast M.2 SSD. First I deleted former F36 partitions already on it, then I created the following mount points (in Btrfs):

/root00 (220 GB) = nvme0n1p3
/boot (2 GB)
BIOSBoot (2 MB) = nvme0n1p2
swap (6 GB) = nvme0n1p4
/home (220 GB)

while retaining the EFI System Partition already existing (this was perhaps my fault).
Data were already stored on a separate hard disk.

When I rebooted, it did not start, and if I force to start from M.2 SSD, it reads:

Reboot and Select proper Device
or Insert Boot Media in selected Boot device and press a key

Then I tried to check the disk:

fdisk -l
    Disk /dev/nvme0n1: 232.89 GiB, 250059350016 bytes, 488397168 sectors
    Disk model: KINGSTON SA2000M8250G                   
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: A7..........4F

    Dispositivo       Start      Fine   Settori  Size Tipo
    /dev/nvme0n1p1     2048   2099199   2097152    1G EFI System
    /dev/nvme0n1p2  2099200   2103295      4096    2M BIOS boot
    /dev/nvme0n1p3  2103296   6297599   4194304    2G Linux filesystem
    /dev/nvme0n1p4  6297600  18880511  12582912    6G Linux swap
    /dev/nvme0n1p5 18880512 480253951 461373440  220G Linux filesystem

    GPT PMBR size mismatch (4675131 != 8013453) will be corrected by write

Thus, chances are that I messed out with new partitions.
I also assume, that if the right command is executed, the GPT PMBR will be fixed, as it is written there. Am I right, or am I just making things much more simple than they are?
Otherwise, which is that command (write, as such, is something different, I know)? And above all, which is the right syntax?
More helpful suggestion?

Thanks a lot for any advice

The biosboot partition is only used if booting in legacy (MBR) mode.
The efi partition is only used if booting in uefi mode.

Which way was the install done, and which mode is used for booting.?
To know the boot mode, if the command cat /sys/firmware/efi/efivars returns the below result then you are booted in efi mode.

$ cat /sys/firmware/efi/efivars/
cat: /sys/firmware/efi/efivars/: Is a directory

To confirm the filesystems and mountpoint of partitions the command lsblk -f should show that, even when booted from the live media.

The efi partition should only be about 200MB and the boot partition should be about 500 - 750MB. A swap partition is not needed on most fedora installations since the default swap is done using zram in memory. (Swap will be needed if intending to do hibernation or if RAM is extremely small)

It also appears you placed /boot into the btrfs file system which can be done but requires some special config to load the kernel, etc. from a btrfs config.

A default automatic install (on uefi) normally creates 3 partitions.
/boot/efi (approx 200MB) as FAT32) EFI System Partition
/boot (approx 600MB) ext4
A btrfs volume for the remainder, containing /root subvolume mounted at / and /home subvolume mounted at /home.

Looks like /boot is a btrfs subvolume where it should be where /dev/nvme0n1p2 gets mounted.
Can you show us the /etc/fstab?

No, you did it all wrong.
You need, for uefi in fedora:

Tons on info on the net.

and so on.

thank to everybody, you made me realize that I did something wrong at the beginning of the live install.
Thus, yesterday I first canceled all partitions on nvme0 (ssd M.2) through KDE partition manager.
Then I rerun the whole process “Install to hard disk” from the live spin on USB: I avoided the LVM partitioning by choosing customization, but then I let Anaconda do his job automatically.
As a matter of fact, it duly created /boot/efi and /boot as separate partitions (resp., 600 MB and 1024MB), plus / (root, better: root00) and /home both in Btrfs spanning the rest of the volume (231,3 GB). It copied a few gigabytes of programs afterwards.
After restart, my Linux machine booted directly in Fedora 37 grub, I entered with no hassle, updated all programs (something less than 1000 packages) and could work at once.
Have a good time with Fedora!