Point-to-point-encrypted means it can theoretically[1] be read by the vendor (Telegram in this case) or anyone who can coerce the vendor. This is the standard for mail, online banking etc.
The reason for providing both end-to-end-encrypted and point-to-point-encrypted is that point-to-point-encryption is significantly simpler, which makes it easiee to create useful and or cool features.
[1]: vendors can do a nunber of things to make it hard/next to impossible for employees and others to access data, like for example restricting access to user data to service accounts, only allow debugging access in special circumstances and auditing such debugging access.
Telegram used to claim they solve it by sending/storing encrypted data through/in different data centers from the keys, and keeping these days centers in different jurisdictions. Done properly should mean that two or more employees across the company would have to conspire to get access to customer data, or two or more judges in different countries would have to demand data.
But unlike with end-to-end-encryption we have to take their word for it.
My most understanding reading is that you mean Telegram receives the data in plain text at their servers.
That reading implies that they don't do this whole "encrypted data one way, keys another way" thing. (If we know they don't do that I am interested in knowing.)
But a number of people here on HN will read it as "Telegram sends data unencrypted", which is definitely incorrect.