Wiggle it, just a lil bit

pyOpenSci · Oct 28, 2024 · ad2177c · ad2177c
1 parent 50672ce
commit ad2177c
Show file tree

Hide file tree

Showing 4 changed files with 3 additions and 3 deletions.
diff --git 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
@@ -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 → ...ular-code/python-write-expressive-code.md b/clean-modular-code/python-expressive-code.md → ...ular-code/python-write-expressive-code.md
diff --git 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.