Fix test comment

Author: tiif

tests/ui/internal/auxiliary/unstable_feature.rs

@@ -14,7 +14,6 @@ pub struct Bar;
 #[stable(feature = "a", since = "1.1.1" )]
 pub struct Moo;
 
-// Annotate the impl as unstable.
 #[unstable_feature_bound(feat_bar)]
 #[unstable(feature = "feat_bar", issue = "none" )]
 impl Foo for Bar {

tests/ui/internal/unstable-feature-bound-no-effect.rs

@@ -4,8 +4,8 @@
 #![feature(impl_stability)]
 #![allow(dead_code)]
 
-/// If #[unstable(..)] and #[unstable_feature_name(..)] have the same symbol,
-/// The error should not be thrown as it can effectively mark an impl as unstable.
+/// If #[unstable(..)] and #[unstable_feature_name(..)] have the same feature name,
+/// the error should not be thrown as it can effectively mark an impl as unstable.
 ///
 /// If the feature name in #[feature] does not exist in #[unstable_feature_bound(..)]
 /// an error should still be thrown because that feature will not be unstable.

tests/ui/internal/unstable-feature-cross-crate-exact-symbol.rs

@@ -8,8 +8,8 @@
 extern crate unstable_feature;
 use unstable_feature::{Foo, Bar, Moo};
 
-/// Both `feat_foo` and `feat_bar` are needed to use impl
-/// gated by two different unstable feature bound.
+/// To use impls gated by both `feat_foo` and `feat_moo`,
+/// both features must be enabled.
 
 fn main() {
     Bar::foo();

tests/ui/internal/unstable-feature-exact-symbol.fail.stderr

@@ -1,11 +1,11 @@
 error[E0284]: type annotations needed: cannot satisfy `unstable feature: `feat_moo``
-  --> $DIR/unstable-feature-exact-symbol.rs:37:5
+  --> $DIR/unstable-feature-exact-symbol.rs:38:5
    |
 LL |     Bar::moo();
    |     ^^^ cannot satisfy `unstable feature: `feat_moo``
    |
 note: required for `Bar` to implement `Moo`
-  --> $DIR/unstable-feature-exact-symbol.rs:29:6
+  --> $DIR/unstable-feature-exact-symbol.rs:30:6
    |
 LL | #[unstable_feature_bound(feat_moo)]
    | ----------------------------------- unsatisfied trait bound introduced here

tests/ui/internal/unstable-feature-exact-symbol.rs

@@ -7,8 +7,9 @@
 #![allow(dead_code)]
 #![unstable(feature = "feat_foo", issue = "none" )]
 
-/// In staged-api crate, impl that is marked with `feat_moo`
-/// should not be accessible if only `feat_foo` is enabled.
+/// In staged-api crate, impl that is marked as unstable with
+/// feature name `feat_moo` should not be accessible
+/// if only `feat_foo` is enabled.
 
 pub trait Foo {
     fn foo();

tests/ui/internal/unstable-impl-cannot-use-feature.fail.stderr

@@ -1,11 +1,11 @@
 error[E0284]: type annotations needed: cannot satisfy `unstable feature: `feat_foo``
-  --> $DIR/unstable-impl-cannot-use-feature.rs:26:5
+  --> $DIR/unstable-impl-cannot-use-feature.rs:27:5
    |
 LL |     Bar::foo();
    |     ^^^ cannot satisfy `unstable feature: `feat_foo``
    |
 note: required for `Bar` to implement `Foo`
-  --> $DIR/unstable-impl-cannot-use-feature.rs:20:6
+  --> $DIR/unstable-impl-cannot-use-feature.rs:21:6
    |
 LL | #[unstable_feature_bound(feat_foo)]
    | ----------------------------------- unsatisfied trait bound introduced here

tests/ui/internal/unstable-impl-cannot-use-feature.rs

@@ -5,9 +5,10 @@
 #![feature(staged_api)]
 #![feature(impl_stability)]
 #![allow(dead_code)]
-#![cfg_attr(fail, feature(feat_foo))]
 #![unstable(feature = "feat_foo", issue = "none" )]
 
+#![cfg_attr(fail, feature(feat_foo))]
+
 /// In staged-api crate, using an unstable impl requires
 /// #[unstable_feature_bound(..)], not  #[feature(..)].