edits to best practices doc

Signed-off-by: Nell Shamrell <nellshamrell@gmail.com>

docs/best-practice-non-memory-safe-by-default-languages.md

@@ -1,6 +1,6 @@
 # Best Practices - Non Memory-Safe By Default Languages
 
-This working group recommends switching to a memory-safe by default language whenever possible or practical. However, when switching to a memory-safe by default language is not possible or practical, there are developer practices that will improve memory safety, even if it is not the default.
+This working group recommends using a memory-safe by default language whenever possible or practical. However, when using a memory-safe by default language is not possible or practical, there are developer practices that will improve memory safety, even if it is not the default.
 
 ## C
 
@@ -10,3 +10,4 @@ This working group recommends switching to a memory-safe by default language whe
 
 * [Making C++ Memory-Safe Without Borrow Checking, Reference Counting, or Tracing Garbage Collection](https://verdagon.dev/blog/vale-memory-safe-cpp)
 * [C++ Core Guidelines](https://github.com/isocpp/CppCoreGuidelines)
+* [C/C++ Hardening Guide](https://github.com/ossf/wg-best-practices-os-developers/tree/main/docs/Compiler-Hardening-Guides)