It’s already formatted in a way that can be displayed as Objective-C or Swift. But I think ASObjC is a step too far. And even if it could be done, the descriptions would be the same as now. The only stuff you’d be translating would be the syntax stuff that’s the same everywhere, and which is not difficult to learn.
Even if you know Objective-C, the documentation is often insufficient, or unclear. In many cases you need a combination of Google and hunting for example code, and several rounds of trial-and-error.
It’s similar to AppleScript in this respect: knowing AppleScript will get you started scripting an app like InDesign, but you won’t get far unless you understand how the app works, and its object model. So if you decide you want to deal with XML documents, for example, you need to understand XML, and you need to know how the various classes relate to each other. That goes whether you’re using Objective-C or ASObjC, and once you have mastered the simple basics of ASObjC syntax, much of the effort is quite similar.
I think sample code is a huge help, but often snippets don’t lend themselves to universal application – what you need depends a lot on the context.
The good news is you don’t need to know it all, and you can learn bits as you think they will be useful to you.