Update desclaimer on "Hackerrank Solutions: Python 3 and Perl 6 (part 2)"

1 files changed, 5 insertions, 8 deletions

diff --git a/_posts/2018-10-11-hackerrank-solutions-python3-and-perl6-part-2.html b/_posts/2018-10-11-hackerrank-solutions-python3-and-perl6-part-2.html
index 5594bc2..26df2cb 100644
--- a/_posts/2018-10-11-hackerrank-solutions-python3-and-perl6-part-2.html
+++ b/_posts/2018-10-11-hackerrank-solutions-python3-and-perl6-part-2.html
@@ -27,14 +27,11 @@ Additional comments are always welcome as I try to improve the format.
 {% endmarkdown %}
 
 {% admonition_md Disclaimer %}
-Due to some comments I had on the previous article, I want to make some
-additional constraints I adhere to personally clear.
-
-I don't want to make use of `import` (or `use` for Perl 6) statements if these
-were not provided in the challenge template themselves. I do this because I
-want to stick to the challenges as closely as possible. Another reason is
-because it would invite all sorts of discussion that I could've used any module
-for it, and then discuss which module would've solved it best.
+Once again I'd like to make clear I'm trying to stick to the original
+Hackerrank challenges by not using any imports not specifically used in the
+original challenge. If you have suggestions for Python 3 or Perl 6 modules to
+make a given task easier, I still appreciate them, but I won't update my
+solutions to use a module.
 {% endadmonition_md %}
 
 {% markdown %}