README.md in rotp-2.1.2 vs README.md in rotp-3.0.0

- old
+ new

@@ -37,10 +37,11 @@ Optionally, you can provide an issuer which will be used as a title in Google Authenticator. ```ruby totp = ROTP::TOTP.new("base32secret3232", issuer: "My Service") +totp.provisioning_uri("alice@google.com") ``` ### Counter based OTP's ```ruby @@ -66,11 +67,11 @@ Provisioning URI's generated by ROTP are compatible with the Google Authenticator App to be scanned with the in-built QR Code scanner. ```ruby -totp.provisioning_uri("alice@google.com") # => 'otpauth://totp/alice@google.com?secret=JBSWY3DPEHPK3PXP' -hotp.provisioning_uri("alice@google.com", 0) # => 'otpauth://hotp/alice@google.com?secret=JBSWY3DPEHPK3PXP&counter=0' +totp.provisioning_uri("alice@google.com") # => 'otpauth://totp/issuer:alice@google.com?secret=JBSWY3DPEHPK3PXP' +hotp.provisioning_uri("alice@google.com", 0) # => 'otpauth://hotp/issuer:alice@google.com?secret=JBSWY3DPEHPK3PXP&counter=0' ``` This can then be rendered as a QR Code which can then be scanned and added to the users list of OTP credentials.