This note points out a correction to a typographical error in the published version of the article [Opt. Lett.41, 5543 (2016)OPLEDP0146-959210.1364/OL.41.005543].