From ad2177cff79936eeb2e89b90b10b682d085db1ce Mon Sep 17 00:00:00 2001
From: Leah Wasser <leah@pyopensci.org>
Date: Sun, 27 Oct 2024 21:16:46 -0600
Subject: [PATCH] Wiggle it, just a lil bit

---
 clean-modular-code/activity-1/clean-code-activity-1.md          | 2 +-
 clean-modular-code/intro-clean-code.md                          | 2 +-
 ...ython-expressive-code.md => python-write-expressive-code.md} | 0
 code-workflow-logic/write-python-functions.md                   | 2 +-
 4 files changed, 3 insertions(+), 3 deletions(-)
 rename clean-modular-code/{python-expressive-code.md => python-write-expressive-code.md} (100%)

diff --git a/clean-modular-code/activity-1/clean-code-activity-1.md b/clean-modular-code/activity-1/clean-code-activity-1.md
index 5fba57e..a9255f7 100644
--- a/clean-modular-code/activity-1/clean-code-activity-1.md
+++ b/clean-modular-code/activity-1/clean-code-activity-1.md
@@ -20,7 +20,7 @@ Writing clean, modular code takes practice but is a habit worth building. Over t
 
 In this exercise, you'll focus on using three key clean code strategies:
 
-1. [**Use expressive names**](../python-expressive-code): Assign meaningful names to all variables and functions to make your code more readable.
+1. [**Use expressive names**](python-expressive-code): Assign meaningful names to all variables and functions to make your code more readable.
 2. [**Use a Python style guide (PEP8) for consistent syntax**](../python-pep-8): Adhere to PEP8 Python code style rules, including proper spacing and naming conventions, to maintain a consistent and readable codebase.
 3. **Identify opportunities to [make your code DRY (Don't Repeat Yourself)](../python-dry-modular-code)**: In this activity, you will use pseudocode to identify areas where the code can be simplified and made DRY. In the next activity, you will implement DRY best practices using loops and functions. 
 
diff --git a/clean-modular-code/intro-clean-code.md b/clean-modular-code/intro-clean-code.md
index 093ccde..bb1cb3a 100644
--- a/clean-modular-code/intro-clean-code.md
+++ b/clean-modular-code/intro-clean-code.md
@@ -32,7 +32,7 @@ jupyter:
 Intro <self>
 Python Code Style <python-pep-8>
 Don't Repeat Yourself <python-dry-modular-code>
-Expressive Code <python-expressive-code>
+Expressive Code <python-write-expressive-code>
 Write Pseudocode <write-pseudocode>
 :::
 
diff --git a/clean-modular-code/python-expressive-code.md b/clean-modular-code/python-write-expressive-code.md
similarity index 100%
rename from clean-modular-code/python-expressive-code.md
rename to clean-modular-code/python-write-expressive-code.md
diff --git a/code-workflow-logic/write-python-functions.md b/code-workflow-logic/write-python-functions.md
index a332314..72c348b 100644
--- a/code-workflow-logic/write-python-functions.md
+++ b/code-workflow-logic/write-python-functions.md
@@ -29,7 +29,7 @@ jupyter:
 
 To define a function in Python, you need:
 - The `def` keyword to start the function definition.
-- A function name that follows [PEP 8 guidelines](../clean-modular-code/python-expressive-code.md) for naming.
+- A function name that follows [PEP 8 guidelines](python-expressive-code) for naming.
 - Input parameters (optional), defined inside parentheses `()`.
 - A `return` statement that specifies the output of the function.
 - A docstring that explains what the function does and defines the function's inputs and outputs. We suggest that you use numpy style docstrings for scientific Python code.