First of all, I think the English was good enough for a web publication, and the article was perfectly understandable despite a few grammatical errors.  I don't think it's fair to pick on such trivial issues.

Second, I think InfoPath fills a very different role than Access.  Access is a much more capable environment, and is much more powerful than InfoPath. 

The main advantage of InfoPath over Access seems to be its ability to be used in a disconnected non-interactive environment, where batch Insert-only data submission is used.  Data Access Pages were supposed to address this somewhat, but unfortuntely suffered from some rather severe limitations.  I don't really understand why anyone would want to use InfoPath in a connected environment, when better (non-XML-based) tools are available (e.g. Access, .NET.)

From my limited knowledge of InfoPath, it seems to be not at all suitable for the majority of traditional database applications where information workers need to see the existing data (and related data), and to make entries based upon data that already exists.   For my purposes, I can't really see a use for it.  But for those people who require Insert-only interaction, I can see where it might be a reasonable option.