Update README.md

README.md

@@ -320,14 +320,31 @@ If successful, the output will show the modified entry.
 
 Since no policy overlay exists (more on this later), we need to create our own.\
 \
-Check adding one of the core schemas that comes with LDAP.
+Try adding one of the core schemas that comes with LDAP.
 ```
 root@example:/# ldapadd -Q -Y EXTERNAL -H ldapi:/// -f /etc/ldap/schema/corba.ldif
 adding new entry "cn=corba,cn=schema,cn=config"
 ```
-Notice we are using the -Q and -Y EXTERNAL parameters, instead of our usual -x, meaning SASL EXTERNAL authentication. 
+Notice we are using the -Q and -Y EXTERNAL parameters instead of our usual -x, meaning SASL EXTERNAL authentication over the ldapi:/// socket, which we usually use binding as the root account. We need to make use of a real administrative account to continue, like the one we created in the first part.
 If we get a result different from the showed up here, we won't be able to implement any schemas or ACLs, and we should check the dockerfile first, and second the commands we used to run the container as well that we started slapd with the specified parameters before.
-
-
+\
+Check our administrative account was well created, so it has it's own directory so we can add special configurations, such schemas
+```
+root@example:/# ldapsearch -Q -Y EXTERNAL -H ldapi:/// -D "cn=admin,dc=example,dc=com" -b cn=config "(objectclass=olcModuleList)"
+# extended LDIF
+#
+# LDAPv3
+# base <cn=config> with scope subtree
+# filter: (objectclass=olcModuleList)
+# requesting: ALL
+#
+# module{0}, config
+dn: cn=module{0},cn=config
+objectClass: olcModuleList
+cn: module{0}
+olcModulePath: /usr/lib/ldap
+olcModuleLoad: {0}back_mdb
+...
+```
 
 <!--ldappasswd -H ldap://server_domain_or_IP -x -D "cn=admin,dc=example,dc=com" -W -S "uid=bob,ou=people,dc=example,dc=com"-->