minor changes on readmes

Author: JaimeSalas

05-iac/00-terraform/05-incorporando-recursos/07-demo.md

@@ -45,7 +45,7 @@ Cortamos el contenido en `network.tf`
 
 Y lo añadimos a `instances.tf`
 
-```tf
+```ini
 # INSTANCES #
 resource "aws_instance" "nginx1" {
   ami                    = nonsensitive(data.aws_ssm_parameter.ami.value)

05-iac/00-terraform/05-incorporando-recursos/09-demo.md

@@ -42,7 +42,7 @@ Actualizamos `variables.tf`
 -}
 +
 +variable "subnets_cidr_block" {
-+  type        = string
++  type        = list(string)
 +  description = "Subnet cidr block"
 +  default     = ["10.0.0.0/24", "10.0.1.0/24"]
 +}
@@ -113,7 +113,7 @@ resource "aws_route_table_association" "rta-subnet1" {
 
 Actualizamo `instances.tf`
 
-```tf
+```ini
 # INSTANCES #
 resource "aws_instance" "nginx1" {
   ami                    = nonsensitive(data.aws_ssm_parameter.ami.value)
@@ -160,7 +160,7 @@ Necesitamos crear un `security group` adicional para el balanceador de carga, de
 
 Actualizamos `network.tf`
 
-```tf
+```ini
 # SECURITY GROUPS #
 resource "aws_security_group" "nginx-sg" {
   name   = "nginx_sg"

05-iac/00-terraform/05-incorporando-recursos/10-demo.md

@@ -20,7 +20,7 @@ Si buscamos en la documentación `elastic load balancing v2`, encontraremos `aws
 
 > EXERCISE: A partir de la documentación actualizar  `loadbalancer.tf`
 
-```tf
+```ini
 ## aws_lb
 resource "aws_lb" "nginx" {
   name               = "lc_web_alb"

05-iac/00-terraform/06-incorporando-nuevos-providers/15-demo.md

@@ -225,7 +225,7 @@ The final `json` looks like:
 
 Actualizamos `s3.tf`
 
-```tf
+```ini
 # aws_s3_bucket
 resource "aws_s3_bucket" "web_bucket" {
   bucket        = local.s3_bucket_name
@@ -314,7 +314,7 @@ resource "aws_s3_bucket" "web_bucket" {
 
 Actualizamos `s3.tf`
 
-```tf
+```ini
 # ....
 # aws_s3_bucket_object
 resource "aws_s3_bucket_object" "website" {
@@ -341,7 +341,7 @@ resource "aws_s3_bucket_object" "graphic" {
 
 Actualizamos `s3.tf`
 
-```tf
+```ini
 # aws_iam_role
 resource "aws_iam_role" "allow_nginx_s3" {
   name = "allow_nginx_s3"
@@ -386,7 +386,7 @@ Ahora podemos asignar la `policy` al `role`
 
 > EJERCICIO. Crear una `policy` que permita todas las acciones sobre S3.
 
-```tf
+```ini
 # aws_iam_role_policy
 resource "aws_iam_role_policy" "allow_s3_all" {
   name = "allow_s3_all"
@@ -428,7 +428,7 @@ resource "aws_iam_role_policy" "allow_s3_all" {
 
 Por útimo creamos el [perfil de instamcia](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html)
 
-```tf
+```ini
 # aws_iam_instance_profile
 resource "aws_iam_instance_profile" "nginx_profile" {
   name = "nginx_profile"

06-monitoring/00-prometheus/.demos/06-querying-gauges-counters/readme.md

@@ -26,7 +26,7 @@ prometheus-2.32.1.linux-amd64/prometheus \
  --config.file="/opt/prometheus/prometheus.yaml"
 ```
 
-Verify targets at http://10.0.010:9090/targets.
+Verify targets at http://10.0.0.10:9090/targets.
 
 
 ## 1. Gauge