That is a storage spaces pool. Whether it is correct depends on your requirements.
1190 GB pool from 1230 physical is 96.7%, roughly seems reasonable assuming some metadata overhead. 810 usable in a 1190 pool is 68%, consistent for 2 parts data to 1 part parity.
Stripes are using the bigger disks past 300 GB. Would have to mean the extra space is being used in stripes with the smaller disk. See also: Mixing disks of different sizes in a Storage Spaces pool
This is not intuitive; capacities that are multiples of physical disks are easier to understand. Ideally, add same size disks in a quantity that is a multiple of the column counts.
Single parity is not ideal either. Storage Spaces Direct has the usual warning that single parity can only tolerate one failure at a time. Regular Storage Spaces apparently need at least a 5 disk dual mirror to survive two simultaneous disk failures.
So, design the overall storage system for the resilience and capacity you need. For example, a mirrored volume instead, across both 465s would be 450 GB or so usable. Not as much capacity, but easy to understand and possibly well performing.
Always back up important data. Arrays will not survive everything, nor will they prevent deleting data.