Merge pull request #53594 from Chukslord1/update-illustrations-credit

added credits for illustrations

Author: prmerger-automator[bot]

learn-pr/github/developer-use-cases-for-ai-with-github-copilot/includes/4-ai-software-development-lifecycle.md

@@ -4,6 +4,8 @@ GitHub Copilot's capabilities extend beyond individual coding tasks, influencing
 
 :::image type="content" source="../media/the-software-development-life-cycle.png" alt-text="The Software Development Life Cycle.":::
 
+*Image by Akinrefon Shedrack Tobiloba, from ['Understanding the Software Development Life Cycle (SDLC)'](https://codewithshedrack.substack.com/p/understanding-the-software-development/)*
+
 Let's examine how GitHub Copilot can positively impact each stage of the SDLC:
 
 ### Requirement analysis

learn-pr/github/mcp-server/includes/2-simplify-workflow.md

@@ -25,23 +25,21 @@ MCP offers:
 
 ### How MCP clients connect to servers and services
 
-:::image type="content" source="../media/model-context-protocol-architecture.png" alt-text="Diagram showing the interaction between MCP clients and servers across local and internet environments." lightbox="../media/model-context-protocol-architecture.png":::
+An MCP Client (such as Claude, an IDE, or another tool) can interact with MCP Servers and their connected services in three primary ways. The specific approach depends on whether the underlying resources are local or remote.
 
-The above diagram illustrates three common ways that an MCP Client (such as Claude, an IDE, or another tool) can interact with MCP Servers and the services they connect to. Each path shows a different type of communication, depending on whether the resources are local or remote.
+#### Local communication with local data
 
-#### Local communication with local data (top path)
-
-In this scenario, the MCP Client talks directly to an MCP Server running on your machine using the MCP Protocol. That server then connects to a local data source (for example, files, databases, or other resources stored on your computer).
+The MCP Client talks directly to an MCP Server running on your machine using the MCP Protocol. That server then connects to a local data source (for example, files, databases, or other resources stored on your computer).
 
 **When to use it**: This setup is useful for local development, or anytime you want fast access to data that stays private on your machine.
 
-#### Local server as a bridge to remote services (middle path)
+#### Local server as a bridge to remote services
 
-Here, the MCP Client still connects to an MCP Server running locally. But instead of working only with local data, this server bridges to a remote service on the internet by calling its Web APIs.
+The MCP Client still connects to an MCP Server running locally. But instead of working only with local data, this server bridges to a remote service on the internet by calling its Web APIs.
 
 **When to use it**: This model is common when a local tool needs to fetch or update information from a remote service but benefits from having a local server in between—for example, to handle caching, security checks, or data preprocessing.
 
-#### Remote communication over the internet (bottom path)
+#### Remote communication over the internet
 
 In the final setup, the MCP Client connects to an MCP Server that lives entirely on the internet (not on your machine). That remote server then communicates with other external services via Web APIs.