anko-intel commented on code in PR #21090: URL: https://github.com/apache/incubator-mxnet/pull/21090#discussion_r916726087
########## docs/python_docs/python/tutorials/getting-started/gluon_migration_guide.md: ########## @@ -33,41 +33,41 @@ In Gluon2.0, we extend the support to MXNet numpy and numpy extension with simpl - **Gluon Metrics** and **Optimizers**: refactored with MXNet numpy interface and addressed legacy issues. -Adopting these new functionalities may or may not require modifications on your models. But don't worry, this migration guide will go through a high-level mapping from old functionality to new APIs and make Gluon2.0 migration a hassle-free experience. +Adopting these new functionalities may or may not require modifications on your models. But don't worry, this migration guide will go through a high-level mapping from old functionality to new APIs and make Gluon2.0 migration a hassle-free experience. Review Comment: Thank you for the screenshot. I've just observed such behaviour, when fixing documentation. Now I find some tips about it in the documentation: https://www.markdownguide.org/basic-syntax#line-break-best-practices You can see such behaviou if you generate this part documentation: https://github.com/apache/incubator-mxnet/pull/21060/files#diff-f16304c2f893c2e7d51d74dff3892e5e11b39b8043751ade78b0286bc49afbd2L225-L227 for the older version, where such double spaces where probably accidentally missing. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
