Typo in APIs and Microservices Projects intro

Editor assessment

The subject says a typo in the APIs and Microservices Projects intro was fixed, which is fully understandable without the diff and names the affected section precisely. The fix type and client scope are accurate for a content correction served by the client. No body is present, which is justifiable for a small typo fix; there is no motivation a reader needs beyond what the subject says. The PR reference is the only footer and it is well formed. Style is clean throughout: imperative mood, no trailing period, comfortable length, no ticket junk. A small change communicated exactly as a small change should be.