summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMitsuo Tokumori <[email protected]>2023-09-19 14:03:51 -0500
committerMitsuo Tokumori <[email protected]>2023-09-19 14:03:51 -0500
commit14b6efe39936acb81328a965af0da68cf3cc3c86 (patch)
tree2b2824b7a95c3965b49387ea0768ca4038fd8438
parentd108b60389dfd52cd0e996817f1213979a66de78 (diff)
downloadLP1-14b6efe39936acb81328a965af0da68cf3cc3c86.tar.gz
LP1-14b6efe39936acb81328a965af0da68cf3cc3c86.tar.bz2
LP1-14b6efe39936acb81328a965af0da68cf3cc3c86.zip
Fix typo
-rw-r--r--Readme.adoc4
1 files changed, 2 insertions, 2 deletions
diff --git a/Readme.adoc b/Readme.adoc
index ec62be0..71d3230 100644
--- a/Readme.adoc
+++ b/Readme.adoc
@@ -25,8 +25,8 @@ https://drive.google.com/drive/folders/0B8DUIB5m9fukVHZhX1pRZFhHY2M?resourcekey=
Many times, compilation or runtime error messages are not helpful or
borderline cryptic. Debugging tools help a lot. But narrowing down what
component most likely failed is of **great** help. Develop each "module"
-separately, compile and debug frecuently. Make sure each "module" works OK
-before beginning the next.
+separately, compile and debug frequently. Make sure each "module" works fine
+before moving to the next one.
=== Debugging