On https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/langCon_apex_expressions_operators_understanding.htm
it is stated that:

"Unlike Java, == in Apex compares object value equality, not reference equality, except for user-defined types."
"For sObjects and sObject arrays, == performs a deep check of all sObject field values before returning its result. Likewise for collections and built-in Apex objects." 

Why are the two asserts below failing then? If you look at the debug logs with the "Debug Only" option selected you should see that all 3 objects re identical.

Are the asserts below failing for you as well or is it just a glitch in my dev org?

// Two different ways to get a DescribeSObjectResult object 
        DescribeSObjectResult dsor1 = Account.SObjectType.getDescribe();
        DescribeSObjectResult dsor2 = Schema.sObjectType.Account;
        
        // Another way to get the DescribeSObjectResult using the Schema object
        List<DescribeSObjectResult> l =  Schema.describeSObjects(new List<String> {'Account'});
        DescribeSObjectResult dsor3 = l[0];
        
        System.assert(dsor1 == dsor2); // succeeds
       //System.assert(dsor1 == dsor3); // fails
      // System.assert(dsor2 == dsor3); // fails
       System.assert(dsor1.getsObjectType() == dsor3.getsObjectType()); // succeeds
       System.assert(dsor2.getsObjectType() == dsor3.getsObjectType()); // succeeds
        
        // If you look at the debug logs with the "Debug Only" option selected
        // you should see that the objects below are identical
        system.debug('dsor1: ' + dsor1);
        system.debug('dsor2: ' + dsor2);
        system.debug('dsor3: ' + dsor3);