You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ The expire time of the verification URLs can be changed by updating the `auth.ve
29
29
30
30
## Usage
31
31
32
-
Add the `MustVerifyNewEmail` trait to your `User` model and make sure it implements the `MustVerifyEmail` interface as well.
32
+
Add the `MustVerifyNewEmail` trait to your `User` model and make sure it implements the framework's `MustVerifyEmail` interface as well.
33
33
34
34
```php
35
35
<?php
@@ -98,7 +98,7 @@ class User extends Authenticatable implements MustVerifyEmail
98
98
99
99
### Customization
100
100
101
-
You can change the content of the verification mail by editing the published views which can be found in the `resources/views/vendor/verify-new-email` folder. The `verifyNewEmail.blade.php` view will be sent when verifying *updated* email addresses. The `verifyFirstEmail.blade.php` view will be sent when a User verifies its email address for the first time (after registering). Alternatively you set your own custom Mailables in the config file:
101
+
You can change the content of the verification mail by editing the published views which can be found in the `resources/views/vendor/verify-new-email` folder. The `verifyNewEmail.blade.php` view will be sent when verifying *updated* email addresses. The `verifyFirstEmail.blade.php` view will be sent when a User verifies its initial email address for the first time (after registering). Alternatively you set your own custom Mailables classes in the config file:
0 commit comments