some small suggestions

carpentries-lab · Apr 17, 2023 · d1bdc6e · d1bdc6e
1 parent e066a23
commit d1bdc6e
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/_episodes/06-track_changes.md b/_episodes/06-track_changes.md
@@ -296,7 +296,7 @@ types. In particular, version control can be more or less rewarding
 depending on file size and format. First, file comparison in version
 control systems is optimized for plain text files, such as source code.
 The ability to see so-called "diffs" is one of the great joys of version
-control. Unfortunately, Microsoft Office files (like the `.docx` files
+control systems. Unfortunately, Microsoft Office files (like the `.docx` files
 used by Word) or other binary files, e.g., PDFs, can be stored in a
 version control system, but it is not possible to pinpoint specific
 changes from one version to the next. Tabular data (such as CSV files)

diff --git a/_episodes/08-what_next.md b/_episodes/08-what_next.md
@@ -37,7 +37,7 @@ We have covered good practices in several areas:
 
 Good Enough Practices rely on a shared set of principles that span these areas:
 
-- Planning: plan out how to work, and any plan that you can stick to is better than no plan.
+- Planning: plan out how to work. Any plan that you can stick to is better than no plan.
 - Modular organization: organize your data, code, and projects into coherent modules.
 - Names: give good names to your files, folders, and functions, that make them easy to find and to understand.
 - Documentation: explicitly write down everything you and your collaborators need to know in the future.