In your post #16, that diagram shows something I missed at first glance - a 1 to 1 relationship which almost certainly cannot be correct. You've got tblInspections/InspectionID as 1:1 with tblInspectionDetails/InspectionID_FK.
I say it cannot be correct for one of two reasons: EITHER you are using the "...DETAILS" table as an extension of the Inspection table and there really WILL only be one of each, OR you meant something other than 1:1 on the relationship.
In general, proper normalization will never produce 1:1 tables because (based on "purity of purpose") you never need two keys to refer to what is really just one set of data. So you merge 1:1 table UNLESS there is a security issue that requires you to keep some data separate and protected from prying eyes. I saw a few cases like that when I was a Navy contractor on a personnel system. But it is highly rare.
In context, I can't be sure but it seems to me that the InpsectionDetails table should be a child table that lists / enumerates details relating to an inspection that touches many factors (as suggested by your table InspectionItems). And the ...Details vs. ...Items table relationship DOES make sense if the ...Details table really IS a list of individual items in an inspection.