closures - uninitialized vs undefined

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.

先從 closure 文章中關於詞法環境和巢狀函式的部分開始，然後比較 lexenv-nested-makecounter-2.svg 和 lexenv-nested-makecounter-3.svg 中的標籤。驗證這些圖是否應將 與 undefined 區分開來，並且僅在 JavaScript 的行為支持所提議的修正時更新這些 SVG。

由索引模型根據 Issue 內容生成。