Merge pull request #2718 from jasonrandrews/review

Small updates to Gemini install guide and MCP server Learning Path

Author: jasonrandrews

content/install-guides/gemini.md

@@ -122,7 +122,7 @@ Install Gemini CLI globally using npm:
 npm install -g @google/gemini-cli
 ```
 
-This installs the latest version, such as 0.20.0, directly from npm. Homebrew can lag behind npm, so versions might differ.
+This installs the latest version, such as 0.23.0, directly from npm. Homebrew can lag behind npm, so versions might differ.
 
 ### How do I confirm Gemini CLI is working on macOS?
 
@@ -137,7 +137,7 @@ gemini --version
 The output is similar to:
 
 ```output
-0.20.0
+0.23.0
 ```
 
 Start an interactive session to test basic functionality:
@@ -223,7 +223,7 @@ gemini --version
 The output shows the version:
 
 ```output
-0.20.0
+0.23.0
 ```
 
 ### How do I view the available command-line options?
@@ -380,13 +380,32 @@ Start the Gemini CLI and list the tools from the MCP server to verify it's worki
 gemini
 ```
 
-Use the `/tools` command to list the available tools:
+The output shows the MCP server.
+
+```output
+ Using: 1 GEMINI.md file | 1 MCP server
+```
+
+Use the `/mcp` command to list the available tools:
 
 ```console
-/tools
+/mcp
 ```
 
-The Arm MCP server tools are listed in the output. If the arm-mcp server indicates it's still loading, wait a moment and run `/tools` again.
+The Arm MCP server tools are listed in the output. 
+
+```output
+Configured MCP servers:
+
+🟢 arm_mcp_server - Ready (6 tools)
+  Tools:
+  - check_image
+  - knowledge_base_search
+  - mca
+  - migrate_ease_scan
+  - skopeo
+  - sysreport_instructions
+```
 
 If you're facing issues or have questions, reach out to mcpserver@arm.com.
 

content/learning-paths/servers-and-cloud-computing/arm-mcp-server/3-simd-migration.md

@@ -7,7 +7,7 @@ layout: learningpathall
 ---
 ## Migrating SIMD code with AI assistance
 
-{{% notice Note %}} This section uses Visual Studio Code with GitHub Copilot Chat or Copilot Edits. If you're using a different AI assistant, skip to the next section, where you'll configure the same migration workflow using other agentic systems.{{% /notice %}}
+{{% notice Note %}} This section uses Visual Studio Code with GitHub Copilot. If you're using a different AI assistant, skip to the next section, where you'll configure the same migration workflow using other agentic systems.{{% /notice %}}
 
 When migrating applications from x86 to Arm, you might encounter SIMD (Single Instruction, Multiple Data) code that is written using architecture-specific intrinsics. On x86 platforms, SIMD is commonly implemented with SSE, AVX, or AVX2 intrinsics, while Arm platforms use NEON and SVE intrinsics to provide similar vectorized capabilities. Updating this code manually can be time-consuming and challenging. By combining the Arm MCP Server with a well-defined prompt file, you can automate much of this work and guide an AI assistant through a structured, architecture-aware migration of your codebase.