clarify parameter in DefaultPluginManager::alterInfo()

This is exactly the same behavior as drupal_alter()/ModuleHandlerInterface::alter() always has been, so maybe we should just reference to that?

Thanks for the patch!

I would agree with #3, but this documentation is very short, so I think rather than *just* referencing it, we should go ahead and provide the docs, and also provide an @see link to ModuleHandlerInterface::alter().

Also, regardin the current patch:
- "Example" should not be capitalized in "For Example".
- Please do not use "foobar". Use a more representative hook name, like hook_mymodule_mydata_alter().
- In place of "to use", you might use wording like "If your alter hook is called...".
- In place of "you want to pass only", you might use more concise wording that tells what to do, such as just "pass in".

"mymodule_data" is the example used in ModuleHandlerInterface, so let's borrow that here.

Or should we rename the parameter to make it more obvious it isn't just the hook name, like ModuleHandlerInterface does?

The docs there look good. The first comma (before "for example") should be a ; though.

Changing the parameter would be OK, but it looks like $type is the same parameter name as ModuleHandlerInterface::alter($type)?

Hmmm... Can the $type here be an array?
https://api.drupal.org/api/drupal/core!lib!Drupal!Core!Extension!ModuleH...

If so, I think we should definitely make a link to ModuleHandlerInterface::alter()... it seems unlikely for plugin managers that they would want to use an array though?

Good but needs a space after the ; -- thanks! Also, neither "for" nor "example" should be capitalized, since they are in the middle of a sentence.

Thanks, that should do it.

There is a typo in #10, "mymodula_data"

Doh! Missed that. Looks good this time. :)

Thanks again! Committed to 8.x.