Removing duplicate images, documentation

docs/Lama2/docs/explanation/l2format.md

@@ -113,7 +113,7 @@ and its contents are loaded to create a set of variables (local).
 
 In the `l2.env` file, you can specify environment-specific values for variables used in your L2 scripts, such as URLs, authentication tokens, or any other data that may vary depending on the environment in which the API requests are executed.
 
-![l2.env at API level](l2env.png)
+![l2.env at API level](../tutorials/l2env.png)
 
 Go to [Example](../tutorials/examples.md#case-1-l2env-adjacent-to-an-api-file)
 
@@ -125,7 +125,7 @@ The `l2config.env` file serves as a centralized storage for environment variable
 
 The search for `l2config.env` extends from the present directory up to the root directory (`/`). During this process, the variables defined in the root file are loaded and made available for use in all relevant scripts. This approach significantly enhances efficiency and maintainability, as it ensures consistent settings throughout the project while reducing redundancy in configuration data.
 
-![l2config.env at Project root level](l2configAtRoot.png)
+![l2config.env at Project root level](../tutorials/l2configAtRoot.png)
 
 Go to [Example](../tutorials/examples.md#case-2-root-variables)
 
@@ -137,7 +137,7 @@ In situations where both root and local variables share the same variable name,
 
 The local variable's value will always be considered over the root variable, ensuring that specific configurations defined at the local level effectively override any corresponding settings present in the root file. This approach provides developers with granular control and flexibility in tailoring environment variables to suit specific needs within different parts of the project while maintaining the overall structure and organization of configuration settings.
 
-![l2config.env at Project root level](l2envOverideL2config.png)
+![l2config.env at Project root level](../tutorials/l2envOverideL2config.png)
 
 Go to [Example](../tutorials/examples.md#case-3-override-root-variable-with-local-variable)
 

docs/Lama2/site/explanation/l2format.html

@@ -1018,19 +1018,19 @@ <h4 id="api-environment-variables-can-be-defined-locally-in-l2env">API environme
 This file is automatically searched for in the present directory, 
 and its contents are loaded to create a set of variables (local).</p>
 <p>In the <code>l2.env</code> file, you can specify environment-specific values for variables used in your L2 scripts, such as URLs, authentication tokens, or any other data that may vary depending on the environment in which the API requests are executed.</p>
-<p><img alt="l2.env at API level" src="l2env.png" /></p>
+<p><img alt="l2.env at API level" src="../tutorials/l2env.png" /></p>
 <p>Go to <a href="../tutorials/examples.html#case-1-l2env-adjacent-to-an-api-file">Example</a></p>
 <p>Get <a href="https://github.com/HexmosTech/Lama2/tree/main/examples/0023_l2env_declare">Source File</a></p>
 <h4 id="api-environment-variables-can-be-defined-at-project-root-using-l2configenv">API environment variables can be defined at project root using <code>l2config.env</code><a class="headerlink" href="#api-environment-variables-can-be-defined-at-project-root-using-l2configenv" title="Permanent link">&para;</a></h4>
 <p>The <code>l2config.env</code> file serves as a centralized storage for environment variables located at the project root, streamlining the management of configuration settings across all L2 scripts. With this file present, every L2 script within the project automatically inherits the defined variables, effectively eliminating the necessity to duplicate configurations in individual subdirectories using <code>l2.env</code>.</p>
 <p>The search for <code>l2config.env</code> extends from the present directory up to the root directory (<code>/</code>). During this process, the variables defined in the root file are loaded and made available for use in all relevant scripts. This approach significantly enhances efficiency and maintainability, as it ensures consistent settings throughout the project while reducing redundancy in configuration data.</p>
-<p><img alt="l2config.env at Project root level" src="l2configAtRoot.png" /></p>
+<p><img alt="l2config.env at Project root level" src="../tutorials/l2configAtRoot.png" /></p>
 <p>Go to <a href="../tutorials/examples.html#case-2-root-variables">Example</a></p>
 <p>Get <a href="https://github.com/HexmosTech/Lama2/tree/main/examples/0022_l2config_declare">Source File</a></p>
 <h4 id="if-l2configenvroot-variables-are-redeclared-in-l2envlocal">If <code>l2config.env</code>(root) variables are redeclared in <code>l2.env</code>(local)<a class="headerlink" href="#if-l2configenvroot-variables-are-redeclared-in-l2envlocal" title="Permanent link">&para;</a></h4>
 <p>In situations where both root and local variables share the same variable name, the local variable takes precedence over the root variable. This behavior remains consistent, even if both <code>l2config.env</code> (root) and <code>l2.env</code> (local) files reside in the same directory. </p>
 <p>The local variable's value will always be considered over the root variable, ensuring that specific configurations defined at the local level effectively override any corresponding settings present in the root file. This approach provides developers with granular control and flexibility in tailoring environment variables to suit specific needs within different parts of the project while maintaining the overall structure and organization of configuration settings.</p>
-<p><img alt="l2config.env at Project root level" src="l2envOverideL2config.png" /></p>
+<p><img alt="l2config.env at Project root level" src="../tutorials/l2envOverideL2config.png" /></p>
 <p>Go to <a href="../tutorials/examples.html#case-3-override-root-variable-with-local-variable">Example</a></p>
 <p>Get <a href="https://github.com/HexmosTech/Lama2/tree/main/examples/0020_override_project_root_local">Source File</a></p>
 <h3 id="the-environment-file-can-load-results-of-commands">The environment file can load results of commands<a class="headerlink" href="#the-environment-file-can-load-results-of-commands" title="Permanent link">&para;</a></h3>