Skip to content

Commit da8dabb

Browse files
Fix typo
Co-authored-by: Mihai Maruseac <mihai.maruseac@gmail.com>
1 parent cae178e commit da8dabb

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

rfcs/20230621-tf-api-deprecation.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ A TensorFlow API is considered fully deprecated when:
6060
* Ex: if `tf.bar` uses deprecated `tf.foo`, calling `tf.bar` should not trigger a warning.
6161
* As appropriate, examples (e.g. experimental Colab notebooks) are created demonstrating the replacement of any deprecated modules or methods.
6262
* The API is covered by a publicly available _strict mode_ which users can optionally enable to convert warnings to failures, with error messages that guide them to replacements.
63-
* Strict mode is a globally applied state, switched on with `tf.exprimental.enable_strict_mode()`.
63+
* Strict mode is a globally applied state, switched on with `tf.experimental.enable_strict_mode()`.
6464
* Once enabled, ignorable runtime warnings for deprecated APIs will instead be replaced with errors, detailing the deprecation and suggested alternatives.
6565
* Alongside release in TF Nightly, messaging is sent through appropriate communication channels to inform of the upcoming deprecation, rationale, and available substitutes.
6666
* Depending on the nature and scope of deprecation, this may be done at the individual API level or in interrelated block(s).

0 commit comments

Comments
 (0)