diff --git a/docs/release_notes/0.4.html b/docs/release_notes/0.4.html index 8aca281d..a7dbffc0 100644 --- a/docs/release_notes/0.4.html +++ b/docs/release_notes/0.4.html @@ -127,7 +127,7 @@
Now you can get information of the servers hardware and configuration.
-use Rex::Hardware;
+use Rex::Hardware;
use Data::Dumper;
desc "Get Hardware Information";
diff --git a/docs/release_notes/0.51.2.html b/docs/release_notes/0.51.2.html
index 82df7dc8..128852cc 100644
--- a/docs/release_notes/0.51.2.html
+++ b/docs/release_notes/0.51.2.html
@@ -140,7 +140,7 @@ Base
For example, if you have a CentOS server with the hostname web01, this means that if you request the key maxconn Rex will first try to find the key inside cmdb/CentOS/web01.yml and if it doesn't find the Rex will try the next file in the lookup path.
-use Rex -feature => ['0.51'];
+use Rex -feature => ['0.51'];
task "setup", make {
my $maxconn = get cmdb "maxconn";
};
diff --git a/docs/rex_book/writing_modules/getting_information_of_the_environment.html b/docs/rex_book/writing_modules/getting_information_of_the_environment.html
index 46efdc55..785e7182 100644
--- a/docs/rex_book/writing_modules/getting_information_of_the_environment.html
+++ b/docs/rex_book/writing_modules/getting_information_of_the_environment.html
@@ -125,7 +125,7 @@ Getting information of the environment
Rex comes with a hardware gathering module. To display all the things Rex knows about the environment your can create a test task that just dumps all the information.
-use Rex -feature => ['1.0'];
+use Rex -feature => ['1.0'];
task "dump-info", sub {
dump_system_information;