primary and secondary boot loaders

There is an ambiguity in that text actually. Primary boot loader doesn't mean the first stage of a boot loader, and secondary boot loader doesn't mean the second stage of a boot loader.

First stage of a boot loader is the program resides in MBR data which holds partition information and capability to handle very basic disk I/O operations those cannot accomplish to fully load the O.S since MBR boot loader code size is limited to 448-bytes for standart MBR records (lower for spesific O.S implementations, since partition table holds 4*16-Bytes)

First stage of the boot loader's job is to simply load the second stage which now nows the O.S spesifics and it has much more code space. As far as I remember, NTFS second boot loader has 16 512-bytes sectors to load O.S kernel, 8-KBytes.

Primary and secondary terms come in where there are multiple O.S.es to choose to boot. Each O.S has its boot loader that has first and second stages, each boot loader should start from stage one since the primary boot laoder in MBR shouldn't be expected to know about spesifics of the second stages in every boot loader.

Second stages are stored on the beginning of the partition itself which is called VBR, Volume Boot Record.

When there is one O.S to boot, MBR program (IPL) is the first stage and VBR program is the second stage. When there are multiple O.Ss, MBR program becomes the first stage of the primary boot loader, that stage know there are some code in some partition which is second stage to fully load the whole menu and options, and loads it. That second stage knows about the partitions which has VBR, and continues with VBR, now VBR became secondary boot loader.

Yes, I said "each boot loader should start from stage one since the primary boot laoder in MBR shouldn't be expected to know about spesifics of the second stages in every boot loader.". It is why VBR code also has MBR code in itself, too. Windows VBR codes have it.