closures - uninitialized vs undefined

Personne n'a encore pris cette issue.

in [this article](https://javascript.info/closure), we are discussing lexical environments, and the scope of variables.
upon initialization, variables are defined as `` because "[the engine knows about the variable, but it cannot be referenced until it has been declared with `let`](https://javascript.info/closure#step-1-variables)"

later in the article, when referencing nested lexical environments in functions, a variable is initialized as `undefined`. from my understanding, this is incorrect, as the engine knows about the variable, but is not referenced yet since it hasn't been declared.

i believe that we need to change the following SVG's to reflect this change:
https://github.com/javascript-tutorial/en.javascript.info/blob/master/1-js/06-advanced-functions/03-closure/lexenv-nested-makecounter-2.svg
https://github.com/javascript-tutorial/en.javascript.info/blob/master/1-js/06-advanced-functions/03-closure/lexenv-nested-makecounter-3.svg

if this is an incorrect assumption, please help me understand why it's undefined instead of uninitialized! i'd love to learn more about how this all works.

Commencez par les sections sur l’environnement lexical et les fonctions imbriquées de l’article sur les closures, puis comparez les libellés de lexenv-nested-makecounter-2.svg et lexenv-nested-makecounter-3.svg. Vérifiez si les diagrammes doivent distinguer de undefined, et ne mettez à jour ces SVGs que si le comportement de JavaScript confirme la correction proposée.

Rédigé par le modèle d'indexation à partir du texte de l'issue.