Fix more typos in aspect docs

--
MOS_MIGRATED_REVID=123731717

1 files changed, 4 insertions, 4 deletions

diff --git a/site/docs/skylark/aspects.md b/site/docs/skylark/aspects.md
index 6b21af00dc..def865373f 100644
--- a/site/docs/skylark/aspects.md
+++ b/site/docs/skylark/aspects.md
@@ -120,7 +120,7 @@ def _metal_proto_aspect_impl(target, ctx):
         inputs = proto_sources
         outputs = outputs)
     transitive_outputs = set(outputs)
-    for dep in ctx.attrs.deps:
+    for dep in ctx.attr.deps:
         transitive_outputs = transitive_outputs | dep.metal_proto.transitive_outputs
     return struct(
         metal_proto = struct(direct_outputs = outputs,
@@ -128,7 +128,7 @@ def _metal_proto_aspect_impl(target, ctx):
 ```
 
 The implementation function can access the attributes of the target rule via
-[`ctx.rule.attrs`](lib/ctx.html#rule). It can examine providers that are
+[`ctx.rule.attr`](lib/ctx.html#rule). It can examine providers that are
 provided  by the target to which it is applied (via the `target` argument).
 
 Just like a rule implementation function, an aspect implementation function
@@ -140,8 +140,8 @@ returns a struct of providers that are accessible to its dependencies.
 * For the aspect implementation, the values of attributes along which
   the aspect is propagated (from the 'attr_aspect' list) are replaced with
   the results of an application of the aspect to them. For example, if target
-  X has Y and Z in its deps, `ctx.rule.attrs.deps` for A(X) will be [A(Y), A(Z)].
-  In the `_metal_proto_aspect_impl` function above, ctx.rule.attrs.deps will be
+  X has Y and Z in its deps, `ctx.rule.attr.deps` for A(X) will be [A(Y), A(Z)].
+  In the `_metal_proto_aspect_impl` function above, ctx.rule.attr.deps will be
   Target objects that are the results of applying the aspect to the 'deps'
   of the original target to which the aspect has been applied.
   That allows the aspect to examine `metal_proto` provider on them.